Triple
T28420517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munger Ganga Bridge |
E719928
|
entity |
| Predicate | railwayLineCarries |
P848
|
FINISHED |
| Object | Jamalpur–Kiul section |
—
|
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: Jamalpur–Kiul section | Statement: [Munger Ganga Bridge, railwayLineCarries, Jamalpur–Kiul section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayLineCarries Context triple: [Munger Ganga Bridge, railwayLineCarries, Jamalpur–Kiul section]
-
A.
railwayLine
chosen
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
B.
line1RollingStock
Indicates that the rolling stock (e.g., train cars or locomotives) is assigned to or operating on the first line in a multi-line rail system.
-
C.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
D.
railwayLineType
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
E.
hasRailServiceAt
Indicates that a rail transport service operates at or serves a particular location or facility.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 1:33 a.m.