Triple
T28794889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saigon–Loc Ninh railway line |
E727057
|
entity |
| Predicate | hasCurrentNameOfCityAtTerminus |
P155037
|
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: [Saigon–Loc Ninh railway line, hasCurrentNameOfCityAtTerminus, Ho Chi Minh City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentNameOfCityAtTerminus Context triple: [Saigon–Loc Ninh railway line, hasCurrentNameOfCityAtTerminus, Ho Chi Minh City]
-
A.
notableTerminusCity
Indicates that a city is notably recognized as a terminus (endpoint) of a route, line, or network.
-
B.
hasCapitalTerminus
Indicates that a transportation route or line has its endpoint located in a capital city.
-
C.
hasCityServedCurrentName
chosen
Indicates that the current name of a city is the one used in the context of being served (e.g., by a service, route, or organization).
-
D.
currentOfficialNameOfPlace
Indicates that the object is the official name currently in use for the referenced place.
-
E.
currentNameOfCapital
Indicates that the object is the present, officially recognized name of the subject’s capital 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:24 a.m.