Triple
T37015753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ticino |
E916073
|
entity |
| Predicate | hasBaseTunnel |
P21069
|
FINISHED |
| Object | Gotthard Base 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: Gotthard Base Tunnel | Statement: [Ticino, hasBaseTunnel, Gotthard Base Tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseTunnel Context triple: [Ticino, hasBaseTunnel, Gotthard Base Tunnel]
-
A.
hasTunnel
chosen
Indicates that one entity possesses, contains, or is connected by a tunnel to another entity.
-
B.
hasServiceTunnel
Indicates that one entity is connected to or accessed via a dedicated service tunnel associated with another entity.
-
C.
hasTunnelFunction
Indicates that one entity serves as a tunnel or provides a tunneling function for another entity.
-
D.
usesTunnel
Indicates that one entity makes use of a tunnel as a passage or route to reach or connect to another entity.
-
E.
hasTunnelStubs
Indicates that one entity possesses or includes incomplete or partial tunnel segments that connect or are intended to connect to another structure or system.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:14 p.m.