Triple
T18536842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gotthard Base Tunnel |
E452986
|
entity |
| Predicate | startOfRegularService |
P126875
|
FINISHED |
| Object | 11 December 2016 |
—
|
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: 11 December 2016 | Statement: [Gotthard Base Tunnel, startOfRegularService, 11 December 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfRegularService Context triple: [Gotthard Base Tunnel, startOfRegularService, 11 December 2016]
-
A.
firstRegularServiceStarted
chosen
Indicates that the initial instance of a regular, scheduled service or operation began at a specified time.
-
B.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
C.
programStartPeriod
Indicates the time interval during which a program is initially scheduled to begin or become active.
-
D.
startingGuard
Indicates that an entity serves as the primary or first-choice guard in a lineup, formation, or configuration.
-
E.
serviceStartLocation
Indicates the place where a service or operation is initiated or begins.
- 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.