Triple
T4348770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptolemy I Soter |
E97969
|
entity |
| Predicate | startOfReignAsSatrap |
P1506
|
FINISHED |
| Object | 323 BC |
—
|
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: 323 BC | Statement: [Ptolemy I Soter, startOfReignAsSatrap, 323 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfReignAsSatrap Context triple: [Ptolemy I Soter, startOfReignAsSatrap, 323 BC]
-
A.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
B.
reignAsRegentStart
Indicates the point in time when an individual begins exercising ruling authority as a regent on behalf of another.
-
C.
reignAsCoRulerStart
Indicates the time or event when an entity begins to exercise ruling authority jointly with one or more other rulers.
-
D.
reasonForStartOfReign
Indicates the cause, circumstance, or event that led to the beginning of an entity’s reign.
-
E.
ageAtStartOfReign
Indicates the age an individual was when they began their reign or rule.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a6e89c8190b9bf2cccb63839b3 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.