Triple
T9671030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partick railway station |
E234026
|
entity |
| Predicate | hasSubwayPlatforms |
P89525
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Partick railway station, hasSubwayPlatforms, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubwayPlatforms Context triple: [Partick railway station, hasSubwayPlatforms, 1]
-
A.
hasSubway
Indicates that a place is served by or contains a subway (metro) system.
-
B.
hasSubwayComplex
Indicates that one entity contains or is associated with a subway complex as part of its structure or facilities.
-
C.
hasSuburbanPlatforms
Indicates that an entity (typically a railway station or transit hub) includes platforms specifically designated for suburban or commuter train services.
-
D.
hasUndergroundHighSpeedPlatforms
Indicates that an entity is equipped with high-speed transportation platforms located underground.
-
E.
hasRailPlatforms
Indicates that an entity is equipped with one or more rail platforms used for boarding or alighting from trains.
- F. None of above. chosen
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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6949108190b699442e5c2aacf9 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:15 p.m.