Triple
T37704941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azes II |
E939173
|
entity |
| Predicate | possibleReignStart |
P174272
|
FINISHED |
| Object | late 1st century BCE |
—
|
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: late 1st century BCE | Statement: [Azes II, possibleReignStart, late 1st century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleReignStart Context triple: [Azes II, possibleReignStart, late 1st century BCE]
-
A.
possibleReignPeriod
Indicates a time interval during which an entity could have held ruling authority, without asserting that it definitively did so.
-
B.
originatedInReignOf
Indicates that something began, was initiated, or first came into existence during the rule or governing period of a particular ruler or authority.
-
C.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
D.
reignApproximateDates
chosen
Indicates that the time period associated with a ruler’s reign is known only approximately, rather than with precise start and end dates.
-
E.
possibleRuler
Indicates that one entity is a potential or candidate ruler of another entity, without asserting that the rulership is actual or confirmed.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.