Triple
T36365164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saran region |
E895601
|
entity |
| Predicate | railwayJunctionTown |
P14468
|
FINISHED |
| Object | Chhapra |
—
|
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: Chhapra | Statement: [Saran region, railwayJunctionTown, Chhapra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayJunctionTown Context triple: [Saran region, railwayJunctionTown, Chhapra]
-
A.
railwayJunctionFor
chosen
Indicates that a location serves as a junction point where multiple railway lines or routes connect or intersect for a given railway network or service.
-
B.
hasRailwayTown
Indicates that a location is associated with or contains a town characterized by the presence of a railway or railway facilities.
-
C.
hasRailwayStationOn
Indicates that a railway station is located on or serves a particular railway line, route, or network segment.
-
D.
transportationJunctionFor
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
-
E.
railwayZoneJunction
Indicates a junction where multiple railway zones or lines intersect or connect.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:10 p.m.