Triple
T29307233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ho Chi Minh City–Da Nang |
E743127
|
entity |
| Predicate | city2Description |
P58917
|
FINISHED |
| Object | central coastal city |
—
|
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: central coastal city | Statement: [Ho Chi Minh City–Da Nang, city2Description, central coastal city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: city2Description Context triple: [Ho Chi Minh City–Da Nang, city2Description, central coastal city]
-
A.
cityDescribedAs
chosen
Indicates that a city is characterized or portrayed using a particular description, label, or set of attributes.
-
B.
city2
Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
-
C.
cityRepresentation
Indicates that one entity serves as the official or primary representative (such as a government, organization, or office) for a particular city in some context.
-
D.
cityOn
Indicates that a city is geographically located on a specified landform, area, or administrative region.
-
E.
city1
Indicates that the subject is classified as a city.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665a6fbb88190bae8ba90855eadda |
completed | May 2, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 1:14 p.m.