Triple
T29965894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haubersbronn |
E761178
|
entity |
| Predicate | railNetworkNearby |
P25143
|
FINISHED |
| Object | Rems Railway region |
—
|
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: Rems Railway region | Statement: [Haubersbronn, railNetworkNearby, Rems Railway region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railNetworkNearby Context triple: [Haubersbronn, railNetworkNearby, Rems Railway region]
-
A.
nearestRailwayLine
Indicates that one railway line is the closest in distance to a given location or feature compared to all other railway lines.
-
B.
nearestRailwayTerminus
Indicates that one location is the closest railway terminus to another specified place.
-
C.
railInfrastructureServed
Indicates that a rail infrastructure facility or segment is served, accessed, or operated by a particular service, operator, or network.
-
D.
hasNearbyRailway
chosen
Indicates that one entity is located close to a railway associated with or relevant to another entity.
-
E.
providesRailConnectionsWithin
Indicates that an entity offers or facilitates rail transport links connecting locations inside a specified area or region.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6786a5c70819085a5d00be58d67cb |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:30 p.m.