Triple
T2257188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vientiane |
E49753
|
entity |
| Predicate | becameCapitalOfLaos |
P5604
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Vientiane, becameCapitalOfLaos, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameCapitalOfLaos Context triple: [Vientiane, becameCapitalOfLaos, 16th century]
-
A.
tookPowerInSaigon
Indicates that an entity assumed or seized political control or authority in Saigon.
-
B.
succeededAsCapitalBy
Indicates that one capital city has been replaced by another as the official capital of a political entity.
-
C.
reunifiedAsCapitalInYear
Indicates that an entity regained its status as a capital city in a specified year after a period of not holding that status.
-
D.
inauguratedAsCapital
chosen
Indicates that a place was officially declared and established as the capital of a political or administrative entity.
-
E.
servedAsNationalCapitalFrom
Indicates that a place functioned as the national capital of a country or political entity during a specified time 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1570dc88190bb2b17ed4c25dbb5 |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.