Triple
T34669751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Thanh International Airport |
E890344
|
entity |
| Predicate | transportConnectionPlanned |
P164982
|
FINISHED |
| Object | expressway to Ho Chi Minh 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: expressway to Ho Chi Minh City | Statement: [Long Thanh International Airport, transportConnectionPlanned, expressway to Ho Chi Minh City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportConnectionPlanned Context triple: [Long Thanh International Airport, transportConnectionPlanned, expressway to Ho Chi Minh City]
-
A.
transportPlanned
Indicates that an arrangement has been made for something or someone to be transported from one place to another.
-
B.
transportationPlanned
Indicates that an arrangement has been made for someone or something to be transported from one place to another.
-
C.
plannedTransit
Indicates that a transit or trip has been scheduled or arranged to occur, but has not yet taken place.
-
D.
busOperatorPlanned
Indicates that an entity is designated or scheduled to operate a bus service according to a plan.
-
E.
hasPlannedTransportConnection
chosen
Indicates that there is an intended or scheduled transport link (e.g., route, service, or connection) planned to operate between the related entities.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: May 1, 2026, 2:05 a.m.