Triple
T30217151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izzatnagar railway division |
E768237
|
entity |
| Predicate | adjacentDivision |
P168028
|
FINISHED |
| Object | Lucknow NER railway division |
—
|
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: Lucknow NER railway division | Statement: [Izzatnagar railway division, adjacentDivision, Lucknow NER railway division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentDivision Context triple: [Izzatnagar railway division, adjacentDivision, Lucknow NER railway division]
-
A.
hasNeighbouringDivision
chosen
Indicates that one division is directly adjacent to and shares a boundary with another division.
-
B.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
C.
containsDivision
Indicates that one entity includes or encompasses a subdivision or internal division of another entity.
-
D.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
E.
adjacentLandmark
Indicates that one landmark is located directly next to or very near another landmark, with no significant separation between them.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 7:34 p.m.