Triple
T5164364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huế |
E116514
|
entity |
| Predicate | startTimeAsImperialCapital |
P32945
|
FINISHED |
| Object | 1802 |
—
|
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: 1802 | Statement: [Huế, startTimeAsImperialCapital, 1802]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAsImperialCapital Context triple: [Huế, startTimeAsImperialCapital, 1802]
-
A.
timeAsCapitalStart
chosen
Indicates the point in time when a location first became the capital of a political or administrative entity.
-
B.
reunifiedAsCapitalInYear
Indicates that an entity regained its status as a capital city in a specified year after a period of not holding that status.
-
C.
servedAsCapitalDuring
Indicates that a place functioned as the official capital of a political entity during a specified time period.
-
D.
succeededAsCapitalBy
Indicates that one capital city has been replaced by another as the official capital of a political entity.
-
E.
servedAsNationalCapitalUntil
Indicates that a place functioned as the national capital of a country or state up to a specified end date, after which it no longer held that status.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd792936d48190825da8826448c1da |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.