Triple
T7676917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai Route 12 |
E173884
|
entity |
| Predicate | startPoint_description |
P389
|
FINISHED |
| Object | near the Myanmar border at Mae Sot |
—
|
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: near the Myanmar border at Mae Sot | Statement: [Thai Route 12, startPoint_description, near the Myanmar border at Mae Sot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startPoint_description Context triple: [Thai Route 12, startPoint_description, near the Myanmar border at Mae Sot]
-
A.
startPoint
chosen
Indicates the initial location or position from which an object, path, or action begins.
-
B.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
-
C.
startAndFinishLocation
Indicates that an event, journey, or action both begins and ends at the specified location.
-
D.
tourStartingPointSide
Indicates the side or direction from which a tour begins relative to a reference point or route.
-
E.
startCity
Indicates the city where a journey, route, or transportation service begins.
- 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4:01 p.m.