Triple
T35350974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakhon Ratchasima–Nong Khai branch |
E1020877
|
entity |
| Predicate | borderTownTerminus |
P200650
|
FINISHED |
| Object | Nong Khai |
—
|
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: Nong Khai | Statement: [Nakhon Ratchasima–Nong Khai branch, borderTownTerminus, Nong Khai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTownTerminus Context triple: [Nakhon Ratchasima–Nong Khai branch, borderTownTerminus, Nong Khai]
-
A.
borderTerminus
Indicates the endpoint location where a border between two areas or entities begins or ends.
-
B.
borderTerminusNearby
Indicates that the endpoint of a border or boundary lies close to a specified reference location or feature.
-
C.
borderStation
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
-
D.
borderTownAccess
Indicates that an entity has permission or the ability to enter, use, or pass through a town located on or near a border.
-
E.
borderStationFor
Indicates that a particular border station serves, monitors, or is responsible for a specific border crossing or boundary segment.
- F. None of above. chosen
Provenance (4 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69ff9d9ba1ac8190a0cca5764bb5904d |
completed | May 9, 2026, 8:48 p.m. |
Created at: May 3, 2026, 4:03 p.m.