Triple
T27939820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guntur railway division |
E700710
|
entity |
| Predicate | managesRailwayOperationsIn |
P148863
|
FINISHED |
| Object | Guntur region |
—
|
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: Guntur region | Statement: [Guntur railway division, managesRailwayOperationsIn, Guntur region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesRailwayOperationsIn Context triple: [Guntur railway division, managesRailwayOperationsIn, Guntur region]
-
A.
operatesRailNetworkOf
chosen
Indicates that one entity manages and runs the rail network belonging to or associated with another entity.
-
B.
railwayInfrastructureManager
Indicates that one entity is responsible for managing, maintaining, and operating the railway infrastructure used by another entity.
-
C.
trainOperation
Indicates that an entity is engaged in operating, running, or managing the movement and service of a train.
-
D.
operatesRegionalRailServices
Indicates that an entity manages and runs passenger rail transport services within a specific region or set of regions.
-
E.
railwayControlledBy
Indicates that the operation, management, or authority over a railway is exercised by a specified controlling 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 7:16 p.m.