Triple

T30283990
Position Surface form Disambiguated ID Type / Status
Subject Foligno railway station E770179 entity
Predicate servesRailwayLineCategory P21523 FINISHED
Object regional lines 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: regional lines | Statement: [Foligno railway station, servesRailwayLineCategory, regional lines]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesRailwayLineCategory
Context triple: [Foligno railway station, servesRailwayLineCategory, regional lines]
  • A. 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.
  • B. 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).
  • C. railroadLineServed
    Indicates that a particular railroad line provides service to, or operates through, a given location or facility.
  • D. hasRailServiceAt
    Indicates that a rail transport service operates at or serves a particular location or facility.
  • E. servesCommuterRailLine
    Indicates that a location or facility provides access to and is a stop or station for a commuter rail line.
  • 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_69f224868fa8819099127eaf8855a28f completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fe779248c081909f0ed1a2a0df23db completed May 8, 2026, 11:53 p.m.
PD Predicate disambiguation batch_69fe76eaf6d48190998bc7168749cc42 completed May 8, 2026, 11:51 p.m.
Created at: April 29, 2026, 7:45 p.m.