Triple
T25398186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumding railway division |
E636347
|
entity |
| Predicate | overseesRailOperationsIn |
P148863
|
FINISHED |
| Object | Assam |
—
|
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: Assam | Statement: [Lumding railway division, overseesRailOperationsIn, Assam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesRailOperationsIn Context triple: [Lumding railway division, overseesRailOperationsIn, Assam]
-
A.
operatesRailNetworkOf
chosen
Indicates that one entity manages and runs the rail network belonging to or associated with another entity.
-
B.
operatesRegionalRailServices
Indicates that an entity manages and runs passenger rail transport services within a specific region or set of regions.
-
C.
railwayInfrastructureManager
Indicates that one entity is responsible for managing, maintaining, and operating the railway infrastructure used by another entity.
-
D.
trainOperation
Indicates that an entity is engaged in operating, running, or managing the movement and service of a train.
-
E.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 1:50 p.m.