Triple

T34434094
Position Surface form Disambiguated ID Type / Status
Subject rack railway to Drachenfels E883905 entity
Predicate connectsSettlementToSummit P199771 FINISHED
Object Königswinter – Drachenfels 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: Königswinter – Drachenfels | Statement: [rack railway to Drachenfels, connectsSettlementToSummit, Königswinter – Drachenfels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsSettlementToSummit
Context triple: [rack railway to Drachenfels, connectsSettlementToSummit, Königswinter – Drachenfels]
  • A. hasSettlementOnSummit
    Indicates that a settlement is located on or at the summit (top) of a geographic feature.
  • B. hasSummitConnectionTo
    Indicates a relationship where two entities are connected through a shared summit, peak, or highest point, such that one has a direct summit-related linkage to the other.
  • C. hasSummit
    Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
  • D. summitSuccess
    Indicates that an attempt to reach the summit of a peak has been successfully completed.
  • E. reachesSummit
    Indicates that an entity successfully arrives at or attains the highest point or summit of something.
  • 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_69f349c3dd2c819092cc9e64809f4a42 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff56ef0a5c8190ae729d66a8cf7fc4 completed May 9, 2026, 3:46 p.m.
PD Predicate disambiguation batch_69ff539859c481909ec56310da418688 completed May 9, 2026, 3:32 p.m.
PDg Predicate description generation batch_69ff56edc4d081908f1d263e05cbd512 completed May 9, 2026, 3:46 p.m.
Created at: May 1, 2026, 2 a.m.