Triple
T30525579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A32 motorway |
E776830
|
entity |
| Predicate | connectedToTunnel |
P21069
|
FINISHED |
| Object | Fréjus Road Tunnel |
E31991
|
NE 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: Fréjus Road Tunnel | Statement: [A32 motorway, connectedToTunnel, Fréjus Road Tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToTunnel Context triple: [A32 motorway, connectedToTunnel, Fréjus Road Tunnel]
-
A.
tunnelOpened
Indicates that a tunnel has been created or made accessible, establishing an open passage between two locations or systems.
-
B.
usesTunnel
Indicates that one entity makes use of a tunnel as a passage or route to reach or connect to another entity.
-
C.
hasTunnel
chosen
Indicates that one entity possesses, contains, or is connected by a tunnel to another entity.
-
D.
tunnelUse
Indicates that one entity makes use of or passes through a tunnel associated with another entity.
-
E.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
- F. None of above.
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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2856ed03ec8190bc5c173af116d27d |
completed | June 9, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 29, 2026, 8:17 p.m.