Triple

T28772503
Position Surface form Disambiguated ID Type / Status
Subject Belgium E726448 entity
Predicate hasHighSpeedRailConnectionWith 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: [Belgium, hasHighSpeedRailConnectionWith, France]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHighSpeedRailConnectionWith
Context triple: [Belgium, hasHighSpeedRailConnectionWith, France]
  • A. hasHighSpeedRailStation
    Indicates that a location is served by a high-speed rail station where high-speed trains regularly stop.
  • B. hasPassengerRailConnection
    Indicates that there exists a passenger rail service linking one location or transport node to another.
  • C. hasHighSpeedLine chosen
    Indicates that there exists a high-speed rail line connection between the related entities.
  • D. hasBorderRailConnectionWith
    Indicates that two places are directly connected to each other by a cross-border railway line or service.
  • E. railwayConnectsTo
    Indicates that one railway line, track, or network is directly linked or joined to another, allowing trains to move between them.
  • 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_69f03199997c8190b6ae43fb19312443 completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69fd05ba6b2c81909c62b46237d10365 completed May 7, 2026, 9:35 p.m.
PD Predicate disambiguation batch_69fd03039e48819082b6e12c5453885a completed May 7, 2026, 9:24 p.m.
Created at: April 28, 2026, 6:16 a.m.