Triple
T18747950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RailTel Corporation of India |
E458451
|
entity |
| Predicate | routeAlignment |
P28500
|
FINISHED |
| Object | along railway tracks |
—
|
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: along railway tracks | Statement: [RailTel Corporation of India, routeAlignment, along railway tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeAlignment Context triple: [RailTel Corporation of India, routeAlignment, along railway tracks]
-
A.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
B.
primaryStreetAlignment
Indicates that two or more primary streets share the same or a specified relative directional orientation or alignment.
-
C.
hasRouteAlignment
chosen
Indicates that there is a defined spatial or geometric alignment associated with a route or pathway.
-
D.
roadAxis
Indicates a central reference line that defines the primary longitudinal direction or alignment of a road.
-
E.
streetOrientedAlong
Indicates that a street is aligned or runs in the same general direction as a specified reference feature or axis.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579e9903c81908180c46012bd0948 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.