Triple
T3207196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Anshan |
E67191
|
entity |
| Predicate | chronologicalPrecedenceOver |
P33474
|
FINISHED |
| Object | title King of Persia |
—
|
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: title King of Persia | Statement: [King of Anshan, chronologicalPrecedenceOver, title King of Persia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPrecedenceOver Context triple: [King of Anshan, chronologicalPrecedenceOver, title King of Persia]
-
A.
chronologyPrecedes
chosen
Indicates that one event or state occurs earlier in time than another in a chronological sequence.
-
B.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
C.
chronologyPrevious
Indicates that one event, item, or state occurs directly before another in a chronological sequence.
-
D.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
-
E.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaa58340881908347d772cfa0ac4c |
completed | March 8, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.