Triple
T26188752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Königswinter |
E654904
|
entity |
| Predicate | hasMountainRailway |
P173681
|
FINISHED |
| Object | Drachenfels 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: Drachenfels Railway | Statement: [Königswinter, hasMountainRailway, Drachenfels Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMountainRailway Context triple: [Königswinter, hasMountainRailway, Drachenfels Railway]
-
A.
hasMountainRailwayConnectionTo
Indicates that there is a railway line specifically adapted for mountainous terrain that connects one location to another.
-
B.
hasCableCar
Indicates that one entity possesses, operates, or is served by a cable car system connecting it to other locations or points.
-
C.
containsHillStation
Indicates that a geographic region or area includes at least one hill station within its boundaries.
-
D.
hasRopewayTerminal
Indicates that one entity serves as or contains a ropeway (cable car) terminal associated with another entity.
-
E.
isTouristRailway
Indicates that a railway is primarily operated for tourism or leisure purposes rather than as a regular public transport service.
- F. None of above. chosen
Provenance (4 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 26, 2026, 8:43 p.m.