Triple
T4477398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basingstoke railway station |
E100041
|
entity |
| Predicate | hasSubway |
P56786
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Basingstoke railway station, hasSubway, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubway Context triple: [Basingstoke railway station, hasSubway, yes]
-
A.
hasSubwayComplex
Indicates that one entity contains or is associated with a subway complex as part of its structure or facilities.
-
B.
hasMetroLine
Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
-
C.
hasUndergroundConnections
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
-
D.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground level.
-
E.
hasTramway
Indicates that a location or area is served by, contains, or is connected to a tramway system.
- 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
| PDg | Predicate description generation | batch_69b35727a8ac819090420bd3e2cfbcf1 |
completed | March 13, 2026, 12:15 a.m. |
Created at: March 12, 2026, 11:35 p.m.