Triple
T24418749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VN |
E615665
|
entity |
| Predicate | associatedMajorCity |
P24465
|
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: [VN, associatedMajorCity, Ho Chi Minh City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMajorCity Context triple: [VN, associatedMajorCity, Ho Chi Minh City]
-
A.
otherMajorCity
Indicates that one city is another major city associated with or comparable in importance or status to the first city.
-
B.
nearestMajorCity
Indicates that one city is the closest significant urban center to another location or city compared to all other major cities.
-
C.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
D.
principalCityOf
Indicates that a city serves as the main or most important city (often administrative, economic, or cultural center) of a specified region or area.
-
E.
cityAssociatedWith
chosen
Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a12a50819099fcdbc7096b53dd |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:13 a.m.