Triple
T34481364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimaatre |
E885193
|
entity |
| Predicate | associatedWithRulerReignLength |
P22408
|
FINISHED |
| Object | long reign |
—
|
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: long reign | Statement: [Nimaatre, associatedWithRulerReignLength, long reign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRulerReignLength Context triple: [Nimaatre, associatedWithRulerReignLength, long reign]
-
A.
reignLengthsType
Indicates the type or categorization of the duration of a reign (e.g., how a reign’s length is classified).
-
B.
numberOfReigns
Indicates the count of distinct reigns or ruling periods associated with an entity.
-
C.
reignDuration
chosen
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
-
D.
mostReignsNumber
Indicates that the subject holds the highest number of separate reigns or terms in a given role or title compared to all others.
-
E.
dynastyRuled
Indicates that a particular dynasty held ruling authority or governance over a specified region, state, or people during a certain period.
- 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.