Triple
T29648785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Myanmar–Thailand Trilateral Highway |
E756077
|
entity |
| Predicate | segmentLocatedIn |
P124124
|
FINISHED |
| Object | India |
—
|
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: India | Statement: [India–Myanmar–Thailand Trilateral Highway, segmentLocatedIn, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: segmentLocatedIn Context triple: [India–Myanmar–Thailand Trilateral Highway, segmentLocatedIn, India]
-
A.
segmentLocation
chosen
Indicates the spatial or positional relationship specifying where a particular segment is located within a larger structure or context.
-
B.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
C.
regionContains
Indicates that one region spatially encompasses or includes another region within its boundaries.
-
D.
regionRuledLocatedIn
Indicates that the region governed or ruled by an entity is geographically located within a specified larger area or place.
-
E.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66f21ff708190b13e801de63bf603 |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:51 p.m.