Triple
T18536840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gotthard Base Tunnel |
E452986
|
entity |
| Predicate | breakthroughDate |
P26212
|
FINISHED |
| Object | 15 October 2010 |
—
|
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: 15 October 2010 | Statement: [Gotthard Base Tunnel, breakthroughDate, 15 October 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakthroughDate Context triple: [Gotthard Base Tunnel, breakthroughDate, 15 October 2010]
-
A.
dateOfBreakthrough
chosen
Indicates the specific date on which a significant breakthrough or major advance occurred.
-
B.
groundbreakingDate
Indicates the date on which construction officially began for a building, structure, or project (i.e., when ground was first broken).
-
C.
breakthroughBy
Indicates that a significant discovery, innovation, or advance was achieved or brought about by a particular agent or entity.
-
D.
breakthrough
Indicates a significant and often sudden advance or discovery that overcomes a major obstacle in a process, field, or endeavor.
-
E.
eraOfBreakthrough
Indicates the time period during which a significant breakthrough or major advancement occurred.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5340256d08190bf22d2cb064413b2 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.