Triple

T29356484
Position Surface form Disambiguated ID Type / Status
Subject Frankfurt Rhine-Main E744456 entity
Predicate hasMajorMotorways P385 FINISHED
Object Autobahn network 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: Autobahn network | Statement: [Frankfurt Rhine-Main, hasMajorMotorways, Autobahn network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMajorMotorways
Context triple: [Frankfurt Rhine-Main, hasMajorMotorways, Autobahn network]
  • A. hasMajorHighway chosen
    Indicates that a location or area is served by or directly connected to a major highway route.
  • B. isMotorwayIn
    Indicates that a motorway is located within or passes through a specified geographic area or administrative region.
  • C. motorwayServedBy
    Indicates that a motorway is connected to or accessed by a particular service facility, route, or transport service.
  • D. hasMajorTransportInfrastructure
    Indicates that a location possesses significant transportation facilities or networks, such as major roads, railways, ports, or airports, that support substantial movement of people or goods.
  • E. isMajorTrafficRoute
    Indicates that a road or pathway serves as a primary, heavily used route for traffic flow within a transportation network.
  • 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_69f0a79aee588190b490f19d93c6e52d completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69ff38b960808190a8263348f1e5c0e4 completed May 9, 2026, 1:38 p.m.
PD Predicate disambiguation batch_69ff37d97d9c8190849b2bac14f9af1d completed May 9, 2026, 1:34 p.m.
Created at: April 28, 2026, 2:12 p.m.