Triple
T26198576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukaphaa |
E655170
|
entity |
| Predicate | dynastyFoundedDuration |
P160362
|
FINISHED |
| Object | nearly six centuries |
—
|
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: nearly six centuries | Statement: [Sukaphaa, dynastyFoundedDuration, nearly six centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyFoundedDuration Context triple: [Sukaphaa, dynastyFoundedDuration, nearly six centuries]
-
A.
dynastyFoundedIn
Indicates that a particular dynasty was established or came into existence in a specified time or place.
-
B.
dynastyFoundedRuledPeriod
Indicates that a particular dynasty was founded and held ruling authority during a specified historical time period.
-
C.
dynastyFoundedBecame
Indicates that an entity founded a dynasty and subsequently became its ruler or central figure.
-
D.
currentDynastyFoundedYear
Indicates the year in which the currently ruling dynasty was established or came into power.
-
E.
dynastyFoundedRuledRegion
Indicates that a particular dynasty was established and exercised ruling authority over a specified region.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cd8c4608190bdf0cc6142264239 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 8:47 p.m.