Triple
T28535684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suppiluliuma I |
E722155
|
entity |
| Predicate | reignApproximateDates |
P174272
|
FINISHED |
| Object | c. 1344–1322 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: c. 1344–1322 BCE | Statement: [Suppiluliuma I, reignApproximateDates, c. 1344–1322 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignApproximateDates Context triple: [Suppiluliuma I, reignApproximateDates, c. 1344–1322 BCE]
-
A.
reignedFrom
Indicates the time period during which an entity held ruling authority or sovereignty over a domain.
-
B.
reignChronology
Indicates the temporal order or sequence in which different reigns or periods of rule occur relative to one another.
-
C.
reignDuration
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
-
D.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
E.
centuryOfReign
Indicates the century during which a given entity’s reign or rule took place.
- F. None of above. chosen
Provenance (4 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 28, 2026, 3:31 a.m.