Triple
T4837082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balaghat |
E108084
|
entity |
| Predicate | railGaugeHistory |
P28401
|
FINISHED |
| Object | former narrow-gauge railway hub |
—
|
LITERAL FINISHED |
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: former narrow-gauge railway hub | Statement: [Balaghat, railGaugeHistory, former narrow-gauge railway hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railGaugeHistory Context triple: [Balaghat, railGaugeHistory, former narrow-gauge railway hub]
-
A.
railwayGaugeContext
Indicates the specific track gauge standard or measurement that applies to, or is used in, a given railway-related context.
-
B.
usesRailGauge
Indicates that one entity (typically a railway system or line) operates using the specified rail gauge measurement of the other entity.
-
C.
hasRailroadHistoryWith
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
-
D.
hasRailroadHistory
chosen
Indicates that an entity is associated with, involved in, or notable for historical events, operations, or developments related to railroads.
-
E.
railroadMet
Indicates that two or more railroads encountered or connected with each other at a specific place or time.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.