Triple
T29884597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikkim–Jhapa sector crossings |
E758974
|
entity |
| Predicate | locatedInIndianState |
P202251
|
FINISHED |
| Object | Sikkim |
—
|
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: Sikkim | Statement: [Sikkim–Jhapa sector crossings, locatedInIndianState, Sikkim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInIndianState Context triple: [Sikkim–Jhapa sector crossings, locatedInIndianState, Sikkim]
-
A.
partlyLocatedInIndianState
Indicates that an entity is geographically or administratively situated such that only part of it lies within the boundaries of a specified Indian state.
-
B.
isPartOfIndianState
Indicates that one entity is a constituent part or subdivision of an Indian state.
-
C.
locatedInUnionTerritory
Indicates that an entity is geographically situated within a specified union territory.
-
D.
includesIndianStateOrTerritory
Indicates that one entity encompasses, contains, or covers the area of an Indian state or union territory.
-
E.
spokenInIndianState
Indicates that a language is spoken within the geographical boundaries of a specific Indian state.
- 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0067cde0f08190b2cd93af5f00d519 |
completed | May 10, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_6a0065820c8c8190994734433c64a30a |
completed | May 10, 2026, 11:01 a.m. |
| PDg | Predicate description generation | batch_6a0067cd38bc8190a719e9d1a287cd95 |
completed | May 10, 2026, 11:11 a.m. |
Created at: April 29, 2026, 5:59 p.m.