Triple
T19869872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Forest Railway (Schwarzwaldbahn) |
E477483
|
entity |
| Predicate | hasRailwayLineType |
P14639
|
FINISHED |
| Object | main line |
—
|
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: main line | Statement: [Black Forest Railway (Schwarzwaldbahn), hasRailwayLineType, main line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayLineType Context triple: [Black Forest Railway (Schwarzwaldbahn), hasRailwayLineType, main line]
-
A.
railwayLineType
chosen
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
B.
hasRailwayInfrastructureType
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
-
C.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
D.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
E.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658a2cc8481908d134b0b5cf79d06 |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.