Triple
T31642937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest Glen station |
E807505
|
entity |
| Predicate | tunnelConstructionMethod |
P29550
|
FINISHED |
| Object | rock-bored tunnel |
—
|
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: rock-bored tunnel | Statement: [Forest Glen station, tunnelConstructionMethod, rock-bored tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunnelConstructionMethod Context triple: [Forest Glen station, tunnelConstructionMethod, rock-bored tunnel]
-
A.
tunnelConstructionReason
Indicates the reason or purpose for which a tunnel is being, was, or will be constructed.
-
B.
tunnelType
chosen
Indicates the specific kind or classification of a tunnel associated with an entity.
-
C.
tunnelDugBy
Indicates that a tunnel was created or excavated by a particular agent or entity.
-
D.
tunnels
Indicates that one entity passes through, under, or within another entity via a tunnel-like passage or structure.
-
E.
partOfTunnel
Indicates that one entity forms a physical segment or component within the structure or extent of a tunnel.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a91c1d3c8190b7c11e5a75921aff |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:50 p.m.