Triple
T37212750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titwala |
E922652
|
entity |
| Predicate | suburbanRailwayLine |
P177940
|
FINISHED |
| Object | Central line |
—
|
NE NERFINISHED |
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: Central line | Statement: [Titwala, suburbanRailwayLine, Central line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suburbanRailwayLine Context triple: [Titwala, suburbanRailwayLine, Central line]
-
A.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
B.
isSuburbanRailway
Indicates that a railway line, service, or system operates primarily within and around a metropolitan area, typically connecting the city center with its suburbs.
-
C.
railroadLineServed
chosen
Indicates that a particular railroad line provides service to, or operates through, a given location or facility.
-
D.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
E.
lightRailNetwork
Indicates a relationship where an area, city, or region is served by or contains a light rail transit network.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:15 p.m.