Triple
T28976765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wuhlheide Park Railway |
E734428
|
entity |
| Predicate | hasStationNearby |
P77644
|
FINISHED |
| Object | Freizeit- und Erholungszentrum Wuhlheide |
—
|
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: Freizeit- und Erholungszentrum Wuhlheide | Statement: [Wuhlheide Park Railway, hasStationNearby, Freizeit- und Erholungszentrum Wuhlheide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStationNearby Context triple: [Wuhlheide Park Railway, hasStationNearby, Freizeit- und Erholungszentrum Wuhlheide]
-
A.
hasStationNear
chosen
Indicates that one entity has a station located in close proximity to another entity.
-
B.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
C.
hasAdjacentStationOnAC
Indicates that one station is directly next to another station along the AC line or route.
-
D.
hasNearbyBirdStation
Indicates that one entity is located close to a bird observation or monitoring station associated with another entity.
-
E.
hasNearbyBay
Indicates that one entity is located close to or adjacent to a bay associated with the other entity.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: April 28, 2026, 9:09 a.m.