Triple

T4148049
Position Surface form Disambiguated ID Type / Status
Subject LGV Interconnexion Est E89834 entity
Predicate allowsDirection P4069 FINISHED
Object north–south high-speed traffic around Paris 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: north–south high-speed traffic around Paris | Statement: [LGV Interconnexion Est, allowsDirection, north–south high-speed traffic around Paris]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allowsDirection
Context triple: [LGV Interconnexion Est, allowsDirection, north–south high-speed traffic around Paris]
  • A. accessDirection
    Indicates the direction or orientation from which access to something is obtained or permitted.
  • B. allows
    Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
  • C. containsDirectionOf
    Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
  • D. hasDirectionType
    Indicates that something possesses or is associated with a specific type or category of direction.
  • E. hasTrafficDirection chosen
    Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
  • 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_69aed95a59a881909b26e70b42c6811a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af033ef6648190adde17f943d89c78 completed March 9, 2026, 5:28 p.m.
PD Predicate disambiguation batch_69af018c101081909070da5b11e5eb3d completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:43 p.m.