Triple
T25390674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Vietnam |
E636154
|
entity |
| Predicate | hasCurrentNameOfFormerCapital |
P106595
|
FINISHED |
| Object | Ho Chi Minh City |
—
|
NE NERFINISHED |
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: Ho Chi Minh City | Statement: [Southern Vietnam, hasCurrentNameOfFormerCapital, Ho Chi Minh City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentNameOfFormerCapital Context triple: [Southern Vietnam, hasCurrentNameOfFormerCapital, Ho Chi Minh City]
-
A.
formerNameOfCapital
Indicates that one entity was the previous official name of a capital city before it was renamed.
-
B.
formerCapitalOf
Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
-
C.
currentNameOfCapital
chosen
Indicates that the object is the present, officially recognized name of the subject’s capital city.
-
D.
isInFormerCapital
Indicates that an entity is located within a city that previously served as a capital but no longer holds that status.
-
E.
historicalCapitalNow
Indicates that a location currently serves as the capital of an entity for which it also held capital status at some point in the past.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 21, 2026, 1:49 p.m.