Triple

T30224139
Position Surface form Disambiguated ID Type / Status
Subject Pío Baroja stop E768429 entity
Predicate servesTransportFunction P13380 FINISHED
Object urban passenger transport 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: urban passenger transport | Statement: [Pío Baroja stop, servesTransportFunction, urban passenger transport]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesTransportFunction
Context triple: [Pío Baroja stop, servesTransportFunction, urban passenger transport]
  • A. hasTransportFunction chosen
    Indicates that an entity serves to move or carry something (such as people, goods, or signals) from one place or state to another.
  • B. servedByTransportation
    Indicates that a location or entity is provided access or connection by a particular mode or service of transportation.
  • C. servesTransportLinks
    Indicates that one entity provides or supports transportation connections or routes for another entity or area.
  • D. definesTransportFor
    Indicates that one entity specifies or determines the means, method, or system of transport used by another entity.
  • E. usesTransport
    Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
  • 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_69f2248108208190be60bf1af343ce70 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fe6fea4a288190bf8615c5d6bf41b4 completed May 8, 2026, 11:21 p.m.
PD Predicate disambiguation batch_69fe6f774de08190975a2393b9a1fd22 completed May 8, 2026, 11:19 p.m.
Created at: April 29, 2026, 7:35 p.m.