Triple
T33236409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samastipur railway division |
E850839
|
entity |
| Predicate | borderConnectivity |
P199346
|
FINISHED |
| Object | Nepal |
—
|
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: Nepal | Statement: [Samastipur railway division, borderConnectivity, Nepal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderConnectivity Context triple: [Samastipur railway division, borderConnectivity, Nepal]
-
A.
borderStateConnectivity
Indicates that two states share a common border that allows direct connectivity between them.
-
B.
borderingCountryConnectivity
Indicates that two countries share a land or maritime border that allows direct movement or interaction between them.
-
C.
borderConnectionPlanned
Indicates that a border crossing or boundary link between two regions is intended or scheduled to be established in the future.
-
D.
borderStateConnection
Indicates a relationship where one state directly borders or shares a boundary with another state.
-
E.
crossBorderFacilityConnectsTo
Indicates that a cross-border facility provides a direct physical or operational connection between two locations or infrastructures across a 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
| PDg | Predicate description generation | batch_69ff2fb9e46c8190b36b3e0bc84f114c |
completed | May 9, 2026, 12:59 p.m. |
Created at: May 1, 2026, 1:31 a.m.