Triple
T22959067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oracle of Amun |
E570842
|
entity |
| Predicate | AlexanderTheGreatConsultation |
P69246
|
FINISHED |
| Object | recognition as son of Amun |
—
|
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: recognition as son of Amun | Statement: [Oracle of Amun, AlexanderTheGreatConsultation, recognition as son of Amun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AlexanderTheGreatConsultation Context triple: [Oracle of Amun, AlexanderTheGreatConsultation, recognition as son of Amun]
-
A.
AthenianCommander
Indicates that the subject serves as a military commander for the Athenians or the Athenian state.
-
B.
SeleucidCommander
Indicates that an individual serves as a military commander for the Seleucid state or its armed forces.
-
C.
DiodotusArgues
Indicates that Diodotus presents reasoning or arguments in favor of a particular position or course of action.
-
D.
knownToAncientGreeks
chosen
Indicates that something was recognized, identified, or understood by people in ancient Greek societies.
-
E.
roleInAlexiad
Indicates that one entity has a specific role or function within the context of the Alexiad (e.g., as an author, subject, or referenced figure).
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f2ce9c8190977f146771816341 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:47 p.m.