Triple

T31570922
Position Surface form Disambiguated ID Type / Status
Subject A4 motorway (Germany) E805559 entity
Predicate westernTerminusAtBorderWith P171966 FINISHED
Object Netherlands 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: Netherlands | Statement: [A4 motorway (Germany), westernTerminusAtBorderWith, Netherlands]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: westernTerminusAtBorderWith
Context triple: [A4 motorway (Germany), westernTerminusAtBorderWith, Netherlands]
  • A. westernTerminusConnectsTo
    Indicates that the western endpoint or terminus of one route, line, or path is directly connected to another specified route, line, or location.
  • B. westernTerminusCrosses
    Indicates that the western endpoint of a route, line, or path intersects or passes over another feature or boundary.
  • C. westernTerminusNear
    Indicates that the western endpoint of one entity is located close to another entity.
  • D. westernTerminusCountry
    Indicates the country in which the westernmost endpoint of something (such as a route, line, or feature) is located.
  • E. westernTerminusDetail
    Indicates the specific endpoint location or characteristics associated with the western terminus of a route or linear feature.
  • 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_69f348d2ee94819091918d1789398c29 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a956e9b08190bf83547bba8e8147 completed May 3, 2026, 1:48 a.m.
PD Predicate disambiguation batch_69f6a75656e081908739ed9e2f600e42 completed May 3, 2026, 1:39 a.m.
PDg Predicate description generation batch_69f6a8036ab481908019f2f071fa406e completed May 3, 2026, 1:42 a.m.
Created at: April 30, 2026, 10:19 p.m.