Triple

T27159179
Position Surface form Disambiguated ID Type / Status
Subject De Terp E682610 entity
Predicate isLocalStopOn P144940 FINISHED
Object Rotterdam Metro network 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: Rotterdam Metro network | Statement: [De Terp, isLocalStopOn, Rotterdam Metro network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isLocalStopOn
Context triple: [De Terp, isLocalStopOn, Rotterdam Metro network]
  • A. isLocalStopFor chosen
    Indicates that a particular stop or station serves as a stopping point for a local (non-express) service or route.
  • B. hasStopNear
    Indicates that one entity has a stop or stopping point located in close proximity to another entity.
  • C. isLocalOn
    Indicates that something resides or operates on a specific local device, system, or node rather than remotely.
  • D. isPassengerStop
    Indicates that a location serves as a designated place where passengers may board or alight from a vehicle or transport service.
  • E. isSmallStop
    Indicates that something functions as a minor or less significant stop within a route, sequence, or process.
  • 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_69eefaceb2a08190b9659b7f730629f5 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f69383222c81909d8baa04129d5c81 completed May 3, 2026, 12:14 a.m.
PD Predicate disambiguation batch_69f690eb1e948190aab41a89969519a5 completed May 3, 2026, 12:03 a.m.
Created at: April 27, 2026, 9:17 a.m.