Triple
T30796532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumarghat railway station |
E784244
|
entity |
| Predicate | primaryRailAccessPointFor |
P54704
|
FINISHED |
| Object | Kailashahar |
E220832
|
NE 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: Kailashahar | Statement: [Kumarghat railway station, primaryRailAccessPointFor, Kailashahar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRailAccessPointFor Context triple: [Kumarghat railway station, primaryRailAccessPointFor, Kailashahar]
-
A.
primaryRailLinkFor
Indicates that one entity serves as the main or principal rail connection or route for another entity.
-
B.
primaryTerminalFor
Indicates that one entity serves as the main or principal terminal associated with another entity.
-
C.
primaryCorridorServed
Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
-
D.
primaryAccessPoint
chosen
Indicates that one entity serves as the main or principal point through which another entity is accessed or entered.
-
E.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
- F. None of above.
Provenance (4 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0338d1074481909541e6150307e7f8 |
completed | May 12, 2026, 2:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28fb9941f081909002bcd2ced66753 |
completed | June 10, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a03386e7da08190b533cb0e908503dd |
completed | May 12, 2026, 2:25 p.m. |
Created at: April 29, 2026, 8:42 p.m.