Triple
T21526707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hue region |
E531114
|
entity |
| Predicate | timeAsImperialCapitalStart |
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: [Hue region, timeAsImperialCapitalStart, 1802]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAsImperialCapitalStart Context triple: [Hue region, timeAsImperialCapitalStart, 1802]
-
A.
periodAsDeFactoCapitalStart
Indicates the point in time when a location begins functioning as the de facto capital, even if not officially designated as such.
-
B.
timeAsCapitalStart
chosen
Indicates the point in time when a location first became the capital of a political or administrative entity.
-
C.
capitalCityDuringEra
Indicates that a particular city served as the capital of an entity (such as a country or region) during a specified historical era or time period.
-
D.
reunifiedAsCapitalInYear
Indicates that an entity regained its status as a capital city in a specified year after a period of not holding that status.
-
E.
movedImperialCapitalTo
Indicates that a ruler or governing authority relocated the primary seat of imperial government from one capital city to another.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee88515874819085e251c0d297a587 |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.