Triple

T17777874
Position Surface form Disambiguated ID Type / Status
Subject Revolución E443818 entity
Predicate isUrbanRailStation P49108 FINISHED
Object yes 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: yes | Statement: [Revolución, isUrbanRailStation, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isUrbanRailStation
Context triple: [Revolución, isUrbanRailStation, yes]
  • A. isRailwayStation
    Indicates that the subject is a railway station, i.e., a facility where trains regularly stop to pick up or drop off passengers and/or freight.
  • B. hasRailStation
    Indicates that one entity possesses, contains, or is served by a rail station.
  • C. hasRailwayStationRole
    Indicates that an entity holds or is assigned a specific functional role or capacity within the operation or management of a railway station.
  • D. isPublicTransportStation chosen
    Indicates that a location functions as a station or stop used by public transportation services such as buses, trains, trams, or subways.
  • E. isRailwayStationInNetwork
    Indicates that a railway station belongs to, and is served as part of, a particular railway network.
  • 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_69d8b9ef17708190bdf7e2adbf14ddc2 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4871e06a481909cf6d59e49dc21c5 completed April 19, 2026, 7:41 a.m.
PD Predicate disambiguation batch_69e3d8d8e538819084f1584426b41d5e completed April 18, 2026, 7:17 p.m.
Created at: April 10, 2026, 10:12 a.m.