Triple
T32024407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chepauk MRTS station |
E817779
|
entity |
| Predicate | railwayStyle |
P128412
|
FINISHED |
| Object | Indian Railways style |
—
|
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: Indian Railways style | Statement: [Chepauk MRTS station, railwayStyle, Indian Railways style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayStyle Context triple: [Chepauk MRTS station, railwayStyle, Indian Railways style]
-
A.
railwayStationStyle
chosen
Indicates that one entity is designed, built, or decorated in the architectural style characteristic of a particular railway station.
-
B.
cityRailStyle
Indicates that something follows or embodies the characteristic style, design, or operational pattern associated with a city rail system.
-
C.
railwayClass
Indicates the specific classification or category assigned to a railway or railway service within a defined system.
-
D.
originalRailway
Indicates that a railway is the first or initial line from which others in a network, route, or system originate or are derived.
-
E.
railwayAdaptation
Indicates that something has been modified, designed, or adjusted specifically for use with or on a railway system.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 12:17 a.m.