Triple

T19888729
Position Surface form Disambiguated ID Type / Status
Subject Paris–Istanbul E477971 entity
Predicate historicallyOperatedAcross P137712 FINISHED
Object multiple national railway systems 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: multiple national railway systems | Statement: [Paris–Istanbul, historicallyOperatedAcross, multiple national railway systems]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyOperatedAcross
Context triple: [Paris–Istanbul, historicallyOperatedAcross, multiple national railway systems]
  • A. historicallyOperatedIn
    Indicates that an entity carried out its activities or operations within a particular location or context during a past time period.
  • B. operatedAmong
    Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
  • C. operatedBefore
    Indicates that one entity performed an operation or action at an earlier time than another entity.
  • D. operatedAs
    Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
  • E. operatedInRegion
    Indicates that an entity conducted operations or activities within a specified geographic region.
  • F. None of above. chosen

Provenance (4 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_69d8e51f32b08190b3687f4f60353250 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6590c1b9c8190abbfaa04b80713b3 completed April 20, 2026, 4:49 p.m.
PD Predicate disambiguation batch_69e537ecda248190895c96afb6243823 completed April 19, 2026, 8:15 p.m.
PDg Predicate description generation batch_69e543c136b081909cab9394b958390a completed April 19, 2026, 9:06 p.m.
Created at: April 10, 2026, 1:52 p.m.