Triple

T32367904
Position Surface form Disambiguated ID Type / Status
Subject borough of Rhüden E827044 entity
Predicate hasTransportLinksWithin P132153 FINISHED
Object Seesen urban area 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: Seesen urban area | Statement: [borough of Rhüden, hasTransportLinksWithin, Seesen urban area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTransportLinksWithin
Context triple: [borough of Rhüden, hasTransportLinksWithin, Seesen urban area]
  • A. hasGoodTransportLinks
    Indicates that a place is well connected to other locations by efficient and convenient transport options.
  • B. hasPublicTransportConnection
    Indicates that there is an available public transportation link or service connecting the related entities.
  • C. isTransportationLinkBetween chosen
    Indicates that there exists a transportation connection (such as a road, rail, air, or sea route) linking the two entities.
  • D. hasTransportationRelation
    Indicates a relationship in which one entity provides, uses, is connected by, or is otherwise associated with a means or mode of transportation to another entity or location.
  • E. hasTransportationProximityTo
    Indicates that one entity is located near or conveniently accessible to another entity in terms of transportation options or routes.
  • 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_69f349166d548190887b412fe908e2f4 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69ff0b6bc4a88190bf1d38c6ea26bcdc completed May 9, 2026, 10:24 a.m.
PD Predicate disambiguation batch_69ff082a22f4819095ded971dbd8ea7b completed May 9, 2026, 10:10 a.m.
Created at: May 1, 2026, 12:50 a.m.