Triple
T27963043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akhaura ICP |
E704634
|
entity |
| Predicate | borderCheckpointFor |
P137378
|
FINISHED |
| Object | Agartala–Akhaura route |
—
|
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: Agartala–Akhaura route | Statement: [Akhaura ICP, borderCheckpointFor, Agartala–Akhaura route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCheckpointFor Context triple: [Akhaura ICP, borderCheckpointFor, Agartala–Akhaura route]
-
A.
borderStationFor
chosen
Indicates that a particular border station serves, monitors, or is responsible for a specific border crossing or boundary segment.
-
B.
borderPostIs
Indicates that one entity functions as a border post associated with or located at another entity.
-
C.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
D.
hasBorderCheckpointOnOtherSide
Indicates that a border checkpoint is located on the opposite side of a boundary relative to a referenced point or entity.
-
E.
borderPass
Indicates that one entity crosses or moves through the boundary separating two regions or jurisdictions.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 27, 2026, 7:33 p.m.