Triple

T18670580
Position Surface form Disambiguated ID Type / Status
Subject Vaud regional transport system E456463 entity
Predicate coordinationAspect P132215 FINISHED
Object fare integration 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: fare integration | Statement: [Vaud regional transport system, coordinationAspect, fare integration]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coordinationAspect
Context triple: [Vaud regional transport system, coordinationAspect, fare integration]
  • A. coordina
    Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group toward a common goal.
  • B. coordinationStyle
    Indicates how entities organize, align, and manage their joint actions or interactions with one another.
  • C. coordinationFunction
    Indicates a relationship where one entity organizes, aligns, or manages the activities or interactions of other entities to ensure they work together effectively.
  • D. coordinationRule
    Indicates a rule or constraint that governs how multiple entities or actions are coordinated or combined with each other.
  • E. coordinatedWith
    Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
  • F. None of above. chosen

Provenance (4 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_69d8d38f72b4819090a935175d9ca8af completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e556b1140c81908002c27a33c03ae2 completed April 19, 2026, 10:26 p.m.
PD Predicate disambiguation batch_69e478db7a248190a8c6584673773923 completed April 19, 2026, 6:40 a.m.
PDg Predicate description generation batch_69e484133ee48190a80f1889d79f34c9 completed April 19, 2026, 7:28 a.m.
Created at: April 10, 2026, 11:48 a.m.