Triple
T26285635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-bane |
E661129
|
entity |
| Predicate | centralTunnel |
P155518
|
FINISHED |
| Object | Common Tunnel |
—
|
NE NERFINISHED |
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: Common Tunnel | Statement: [T-bane, centralTunnel, Common Tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralTunnel Context triple: [T-bane, centralTunnel, Common Tunnel]
-
A.
usesTunnel
Indicates that one entity makes use of a tunnel as a passage or route to reach or connect to another entity.
-
B.
tunnelUse
chosen
Indicates that one entity makes use of or passes through a tunnel associated with another entity.
-
C.
tunnelLocation
Indicates that one entity is the location or site where a tunnel is situated or passes through in relation to another entity.
-
D.
tunnelType
Indicates the specific kind or classification of a tunnel associated with an entity.
-
E.
isCentralHubOf
Indicates that one entity functions as the primary connecting or coordinating hub for activities, resources, or interactions among multiple other entities.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 26, 2026, 10:04 p.m.