Triple
T18987678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mnemon |
E464597
|
entity |
| Predicate | associatedWithReignLength |
P22408
|
FINISHED |
| Object | one of the longest Achaemenid reigns |
—
|
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: one of the longest Achaemenid reigns | Statement: [Mnemon, associatedWithReignLength, one of the longest Achaemenid reigns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithReignLength Context triple: [Mnemon, associatedWithReignLength, one of the longest Achaemenid reigns]
-
A.
reignLengthsType
Indicates the type or categorization of the duration of a reign (e.g., how a reign’s length is classified).
-
B.
mostReignsNumber
Indicates that the subject holds the highest number of separate reigns or terms in a given role or title compared to all others.
-
C.
reignDuration
chosen
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
-
D.
centuryOfReign
Indicates the century during which a given entity’s reign or rule took place.
-
E.
possibleReignPeriod
Indicates a time interval during which an entity could have held ruling authority, without asserting that it definitively did so.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6618ab881909c0ed94930e42e68 |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.