Triple
T35350975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakhon Ratchasima–Nong Khai branch |
E1020877
|
entity |
| Predicate | connectedCountryViaBorder |
P200396
|
FINISHED |
| Object | Lao People’s Democratic Republic |
—
|
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: Lao People’s Democratic Republic | Statement: [Nakhon Ratchasima–Nong Khai branch, connectedCountryViaBorder, Lao People’s Democratic Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedCountryViaBorder Context triple: [Nakhon Ratchasima–Nong Khai branch, connectedCountryViaBorder, Lao People’s Democratic Republic]
-
A.
borderCountries
Indicates that one country shares a land or maritime boundary with another country.
-
B.
hasCountryBorderWith
Indicates that two countries share a common land or maritime boundary.
-
C.
borderingCountryOfState
Indicates that one country shares a land or maritime boundary directly with the specified state.
-
D.
sharesInternationalBorderWith
Indicates that two geographic or political entities have a common boundary that is recognized as an international border.
-
E.
geographicallyBorders
Indicates that two geographic entities share a common boundary or border.
- 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_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
| PDg | Predicate description generation | batch_69ff878e8334819097e3c4bb5ca6ffa5 |
completed | May 9, 2026, 7:14 p.m. |
Created at: May 3, 2026, 4:03 p.m.