Triple
T11904350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuttgart Stadtbahn |
E283234
|
entity |
| Predicate | hasTunnelSections |
P102159
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Stuttgart Stadtbahn, hasTunnelSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTunnelSections Context triple: [Stuttgart Stadtbahn, hasTunnelSections, yes]
-
A.
hasTunnel
Indicates that one entity possesses, contains, or is connected by a tunnel to another entity.
-
B.
hasTunnelShape
Indicates that something possesses a form or configuration resembling a tunnel, typically elongated, enclosed, and passage-like.
-
C.
hasTunnelsOnRoad
Indicates that a road includes or passes through one or more tunnels along its route.
-
D.
hasRailwayTunnel
Indicates that one entity contains, includes, or is connected by a railway tunnel associated with the other entity.
-
E.
operatorOfTunnelSection
Indicates that an entity is responsible for operating or managing a specific section of a tunnel.
- F. None of above. chosen
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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e525460c81909d855048d9c799bf |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.