Triple
T21391201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Street station |
E527652
|
entity |
| Predicate | isUndergroundStructure |
P98017
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Old Street station, isUndergroundStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUndergroundStructure Context triple: [Old Street station, isUndergroundStructure, true]
-
A.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
B.
hasUndergroundLevel
chosen
Indicates that one entity possesses or includes a level, floor, or section that is located below ground level.
-
C.
isInCavernSystem
Indicates that one entity is located within or forms part of an interconnected network of underground caverns associated with another entity.
-
D.
hasUndergroundVestibule
Indicates that one entity possesses or includes an underground vestibule space connected to it.
-
E.
isUndergroundOnly
Indicates that something exists, operates, or is accessible exclusively below ground level and not above ground.
- 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b113690c81909c0a378fddba5d3a |
completed | April 22, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:13 p.m.