Triple
T7614329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharagpur |
E172321
|
entity |
| Predicate | hasRailwayColony |
P522
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kharagpur, hasRailwayColony, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayColony Context triple: [Kharagpur, hasRailwayColony, yes]
-
A.
hasRailroadHistoryWith
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
-
B.
hasRailSystem
chosen
Indicates that an entity possesses or is served by a rail-based transportation system.
-
C.
hasRackRailway
Indicates that one entity possesses or includes a rack railway system connecting locations or operating within its area.
-
D.
hasRailwayInfrastructureType
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
-
E.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa418ef081908fd17ff367520995 |
completed | March 27, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:55 p.m.