Triple
T32312734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brenner Pass |
E825543
|
entity |
| Predicate | BrennerBaseTunnelPlannedUse |
P12134
|
FINISHED |
| Object | high-speed rail underpass |
—
|
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: high-speed rail underpass | Statement: [Brenner Pass, BrennerBaseTunnelPlannedUse, high-speed rail underpass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BrennerBaseTunnelPlannedUse Context triple: [Brenner Pass, BrennerBaseTunnelPlannedUse, high-speed rail underpass]
-
A.
tunnelConstructionReason
Indicates the reason or purpose for which a tunnel is being, was, or will be constructed.
-
B.
tunnelUse
Indicates that one entity makes use of or passes through a tunnel associated with another entity.
-
C.
tunnelsBuiltDuring
Indicates that the construction of a tunnel occurred within the time period or event specified by the related entity.
-
D.
plannedUseOf
chosen
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
E.
hasRailwayTunnel
Indicates that one entity contains, includes, or is connected by a railway tunnel associated with the other entity.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bdb8755481908645da7ceef44e17 |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:46 a.m.