Triple

T31437771
Position Surface form Disambiguated ID Type / Status
Subject Paris–Marseille TGV route E801980 entity
Predicate connectsBodyOfWaterRegion P147860 FINISHED
Object Mediterranean coast 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: Mediterranean coast | Statement: [Paris–Marseille TGV route, connectsBodyOfWaterRegion, Mediterranean coast]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsBodyOfWaterRegion
Context triple: [Paris–Marseille TGV route, connectsBodyOfWaterRegion, Mediterranean coast]
  • A. connectsBodyOfWater
    Indicates a relationship where one entity serves as a link or passage between two bodies of water, allowing them to be joined or interact.
  • B. connectsToBodyOfWaterRegion chosen
    Indicates that a region has a direct physical connection or boundary with a body of water.
  • C. waterbodyRegion
    Indicates that a water body is located within, associated with, or spans a particular geographic region.
  • D. connectedBodyOfWater
    Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
  • E. formsBodyOfWater
    Indicates that one entity constitutes or creates the physical substance or structure that makes up a particular body of water.
  • 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_69f348c475348190bf579ca858eec77c completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fe9dfaa2d08190b2084f63f842eb6b completed May 9, 2026, 2:37 a.m.
PD Predicate disambiguation batch_69fe9bba947c81908b0b2b92a4d19b37 completed May 9, 2026, 2:28 a.m.
Created at: April 30, 2026, 9:03 p.m.