Triple

T24023805
Position Surface form Disambiguated ID Type / Status
Subject Avant E594895 entity
Predicate serviceCategoryWithinRenfe P21523 FINISHED
Object high-speed and long-distance services 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: high-speed and long-distance services | Statement: [Avant, serviceCategoryWithinRenfe, high-speed and long-distance services]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: serviceCategoryWithinRenfe
Context triple: [Avant, serviceCategoryWithinRenfe, high-speed and long-distance services]
  • A. railServiceType chosen
    Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
  • B. railServicesTo
    Indicates that rail transportation services operate from one location to another specified destination.
  • C. railAuthority
    Indicates that an entity has official regulatory or operational control over railway systems or services.
  • D. railwayStationCategory
    Indicates the classification or type category assigned to a railway station within a rail network or system.
  • E. servesLocalTrains
    Indicates that a station or facility provides service or stops specifically for local (non-express) train routes.
  • 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_69e288be2c288190a3a46006945557f7 completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1d7680d5c81908d6a670159879236 completed April 29, 2026, 10:03 a.m.
PD Predicate disambiguation batch_69f17639d23c8190bed93434e2f9230a completed April 29, 2026, 3:08 a.m.
Created at: April 17, 2026, 9:52 p.m.