Triple
T27171260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Alps transport network |
E682914
|
entity |
| Predicate | includesNotableTunnel |
P179988
|
FINISHED |
| Object | Mont Blanc 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: Mont Blanc Tunnel | Statement: [Western Alps transport network, includesNotableTunnel, Mont Blanc Tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesNotableTunnel Context triple: [Western Alps transport network, includesNotableTunnel, Mont Blanc Tunnel]
-
A.
notableTunnel
chosen
Indicates that there is a tunnel associated with the subject that is recognized as significant or noteworthy in some context.
-
B.
usesTunnel
Indicates that one entity makes use of a tunnel as a passage or route to reach or connect to another entity.
-
C.
includesNotablePass
Indicates that an entity (such as a route, trail, or path) contains or goes through a specific notable pass.
-
D.
hasTunnel
Indicates that one entity possesses, contains, or is connected by a tunnel to another entity.
-
E.
tunnelAllows
Indicates that a tunnel provides a passage or route that permits movement, access, or flow between two locations or 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 27, 2026, 9:23 a.m.