Triple

T30817630
Position Surface form Disambiguated ID Type / Status
Subject Belgian transport infrastructure E784826 entity
Predicate highSpeedLinesConnectsTo P48478 FINISHED
Object France 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: France | Statement: [Belgian transport infrastructure, highSpeedLinesConnectsTo, France]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: highSpeedLinesConnectsTo
Context triple: [Belgian transport infrastructure, highSpeedLinesConnectsTo, France]
  • A. hasHighSpeedLine chosen
    Indicates that there exists a high-speed rail line connection between the related entities.
  • B. railwayConnectsTo
    Indicates that one railway line, track, or network is directly linked or joined to another, allowing trains to move between them.
  • C. providesRailConnectionsWithin
    Indicates that an entity offers or facilitates rail transport links connecting locations inside a specified area or region.
  • D. connectsToTransportCorridor
    Indicates that one entity has a direct linkage or access route to a designated transport corridor (such as a road, rail line, or similar transit pathway).
  • E. hasHighSpeedSections
    Indicates that the entity includes segments or portions where operation or movement occurs at high speed.
  • 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_69f224b4eda48190bd212ce4f3901e56 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6906994e88190a2da183455bdf076 completed May 3, 2026, 12:01 a.m.
PD Predicate disambiguation batch_69f68b7d2794819092fef8a63f4f3de8 completed May 2, 2026, 11:40 p.m.
Created at: April 29, 2026, 8:44 p.m.