Triple
T26048041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wangerooge Island Railway |
E647886
|
entity |
| Predicate | isOnlyRailwayOn |
P51883
|
FINISHED |
| Object | Wangerooge |
—
|
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: Wangerooge | Statement: [Wangerooge Island Railway, isOnlyRailwayOn, Wangerooge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnlyRailwayOn Context triple: [Wangerooge Island Railway, isOnlyRailwayOn, Wangerooge]
-
A.
isOnlyRailSystemIn
chosen
Indicates that the subject rail system is the sole rail system operating within the specified area or jurisdiction.
-
B.
isOnlyRailStationServing
Indicates that one rail station is the sole station providing service to a particular area, route, or entity, with no alternative rail stations serving it.
-
C.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
D.
isOnRailway
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
-
E.
isRailInfrastructure
Indicates that something functions as or is classified as part of a railway-related physical infrastructure or system.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6065c200881908080a1069c63207b |
completed | May 2, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 9:10 a.m.