Triple
T13378665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Put |
E319256
|
entity |
| Predicate | roleInEzekiel30 |
P27433
|
FINISHED |
| Object | ally of Egypt |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: ally of Egypt | Statement: [Put, roleInEzekiel30, ally of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInEzekiel30 Context triple: [Put, roleInEzekiel30, ally of Egypt]
-
A.
roleInEschatology
Indicates the role or function an entity is believed to have within doctrines, narratives, or expectations about the end times or ultimate destiny of the world.
-
B.
roleInExodusTradition
Indicates having a specific function, status, or significance within the narratives, practices, or interpretations associated with the Exodus tradition.
-
C.
biblicalFigureRole
chosen
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
D.
symbolicRoleInProphecy
Indicates that an entity serves as a symbolic figure or sign within a prophecy, representing or foreshadowing specific events, themes, or outcomes.
-
E.
roleInThirtyTyrants
Indicates that an entity held a specific role or position within the regime known as the Thirty Tyrants.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce56c6c8190adf4e19f6d1bc233 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.