Triple
T25921232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zirndorf |
E653175
|
entity |
| Predicate | connectedByRailwayLine |
P848
|
FINISHED |
| Object | Nuremberg–Cadolzburg railway |
—
|
NE NERFINISHED |
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: Nuremberg–Cadolzburg railway | Statement: [Zirndorf, connectedByRailwayLine, Nuremberg–Cadolzburg railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedByRailwayLine Context triple: [Zirndorf, connectedByRailwayLine, Nuremberg–Cadolzburg railway]
-
A.
railwayConnectsTo
Indicates that one railway line, track, or network is directly linked or joined to another, allowing trains to move between them.
-
B.
providesRailConnectionsWithin
Indicates that an entity offers or facilitates rail transport links connecting locations inside a specified area or region.
-
C.
railwayLine
chosen
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
D.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
E.
ownsRailwayLine
Indicates that one entity has legal ownership or control over a railway line used for train operations.
- 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 22, 2026, 8:32 a.m.