Triple
T25024141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 717 |
E626660
|
entity |
| Predicate | notableTunnel |
P179988
|
FINISHED |
| Object | Northern City Line tunnels into Moorgate |
—
|
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: Northern City Line tunnels into Moorgate | Statement: [British Rail Class 717, notableTunnel, Northern City Line tunnels into Moorgate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTunnel Context triple: [British Rail Class 717, notableTunnel, Northern City Line tunnels into Moorgate]
-
A.
tunnelUse
Indicates that one entity makes use of or passes through a tunnel associated with another entity.
-
B.
usesTunnel
Indicates that one entity makes use of a tunnel as a passage or route to reach or connect to another entity.
-
C.
tunnelType
Indicates the specific kind or classification of a tunnel associated with an entity.
-
D.
tunnels
Indicates that one entity passes through, under, or within another entity via a tunnel-like passage or structure.
-
E.
notableGate
Indicates that a gate is recognized as significant, prominent, or noteworthy in some context.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 18, 2026, 6:07 a.m.