Triple

T38052434
Position Surface form Disambiguated ID Type / Status
Subject Culoz E949800 entity
Predicate hasRailwayServiceTo P154206 FINISHED
Object Lyon 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: Lyon | Statement: [Culoz, hasRailwayServiceTo, Lyon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRailwayServiceTo
Context triple: [Culoz, hasRailwayServiceTo, Lyon]
  • A. hasRailServiceAt chosen
    Indicates that a rail transport service operates at or serves a particular location or facility.
  • B. isRailServiceOf
    Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
  • C. hasRegionalTrainService
    Indicates that a location or route is served by regional train services connecting it to nearby areas.
  • D. hasNightTrainService
    Indicates that a transportation route or station is served by trains that operate during nighttime hours.
  • E. railwayTypeServed
    Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
  • 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_69f76f000cf081908c11fb5443b392e6 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fe12a899d4819080d48423f32eace9 completed May 8, 2026, 4:43 p.m.
PD Predicate disambiguation batch_69fe0d7f6aa08190a1d2dfc025d4e0dc completed May 8, 2026, 4:21 p.m.
Created at: May 3, 2026, 4:20 p.m.