Triple
T21526708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hue region |
E531114
|
entity |
| Predicate | timeAsImperialCapitalEnd |
P26428
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Hue region, timeAsImperialCapitalEnd, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAsImperialCapitalEnd Context triple: [Hue region, timeAsImperialCapitalEnd, 1945]
-
A.
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.
-
B.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
C.
periodAsDeFactoCapitalStart
Indicates the point in time when a location begins functioning as the de facto capital, even if not officially designated as such.
-
D.
vassalageEndTime
Indicates the point in time at which a vassalage relationship between two entities formally ends.
-
E.
timePeriodAsSeatOfGovernmentEnd
chosen
Indicates the point in time when a particular location ceases to serve as the seat of government for an entity.
- 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.