Triple
T19342526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Sisavang Vong |
E483791
|
entity |
| Predicate | reignStartAsKingOfLuangPrabang |
P135488
|
FINISHED |
| Object | 1904 |
—
|
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: 1904 | Statement: [King Sisavang Vong, reignStartAsKingOfLuangPrabang, 1904]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignStartAsKingOfLuangPrabang Context triple: [King Sisavang Vong, reignStartAsKingOfLuangPrabang, 1904]
-
A.
reignStartAsKingOfBavaria
Indicates the date or point in time when an individual began their reign as King of Bavaria.
-
B.
reignStartAsKingOfWestFrancia
Indicates the date or event when an individual began their reign as king of West Francia.
-
C.
reignAsRajaPermaisuriAgongStart
Indicates the time at which an individual begins their tenure serving as the Raja Permaisuri Agong (Queen Consort) of Malaysia.
-
D.
reignStartAsKingOfEastFrancia
Indicates the date or event when an individual began their reign as king of East Francia.
-
E.
reignAsCrownPrinceFrom
Indicates the period during which a person holds and exercises the official status and role of crown prince of a particular realm or title.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185795bc8190a63061ca794c0d67 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:33 p.m.