Triple
T8747529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braunschweig Hauptbahnhof |
E207868
|
entity |
| Predicate | isJunctionStation |
P14465
|
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: [Braunschweig Hauptbahnhof, isJunctionStation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isJunctionStation Context triple: [Braunschweig Hauptbahnhof, isJunctionStation, yes]
-
A.
junctionStation
chosen
Indicates that a station functions as a junction where multiple routes or lines intersect or connect.
-
B.
isTransportHubBetween
Indicates that a location functions as a central node facilitating transportation connections between two or more other places.
-
C.
isTransportHubType
Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or terminal).
-
D.
isNumberedJunctionOf
Indicates that a junction (such as a road or rail intersection) has been assigned an official identifying number within a network.
-
E.
isMajorStationOn
Indicates that a station serves as a primary or significant stop on a particular route or line.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5da2d67c819094b2b39c78384d0d |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.