Triple
T19623995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antiochus III of Commagene |
E471085
|
entity |
| Predicate | reignEndBefore |
P2721
|
FINISHED |
| Object | 20 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: 20 BC | Statement: [Antiochus III of Commagene, reignEndBefore, 20 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignEndBefore Context triple: [Antiochus III of Commagene, reignEndBefore, 20 BC]
-
A.
reignClaimedEnd
Indicates the point in time or event at which a previously asserted or claimed reign or rule is considered to have ended.
-
B.
endOfReign
chosen
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
C.
appliesAfterReignOf
Indicates that something becomes relevant, valid, or in effect only after the reign or rule of a specified entity has ended.
-
D.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
E.
reignPreceded
Indicates that one entity’s reign occurred immediately before another entity’s reign in a temporal succession.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e8695c81909268c5a91cdbb7fa |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.