Triple
T4035039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St George's Cross subway station |
E83807
|
entity |
| Predicate | hasUndergroundStructure |
P15152
|
FINISHED |
| Object | tunnels |
—
|
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: tunnels | Statement: [St George's Cross subway station, hasUndergroundStructure, tunnels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndergroundStructure Context triple: [St George's Cross subway station, hasUndergroundStructure, tunnels]
-
A.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
-
B.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
C.
hasUndergroundSection
chosen
Indicates that an entity includes a portion or segment that is located below ground level.
-
D.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
E.
subterranean
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb11d92481909aaebbc250ff45b9 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.