Triple

T28453042
Position Surface form Disambiguated ID Type / Status
Subject Sistema Único de Boleto Electrónico E716629 entity
Predicate fareSettlement P149109 FINISHED
Object electronic clearing between operators 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: electronic clearing between operators | Statement: [Sistema Único de Boleto Electrónico, fareSettlement, electronic clearing between operators]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareSettlement
Context triple: [Sistema Único de Boleto Electrónico, fareSettlement, electronic clearing between operators]
  • A. resultOfSettlement
    Indicates that something (such as an agreement, status, or outcome) arises as a consequence of a settlement process or settlement decision.
  • B. settlementWith
    Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
  • C. fareIntegration
    Indicates that multiple transportation services or modes share a coordinated fare system, allowing passengers to use a single payment or ticket across them.
  • D. settlementSystem
    Indicates a relationship where a settlement is organized, governed, or structured according to a particular administrative or territorial system.
  • E. fareIntegrator chosen
    Indicates a relationship where one system or entity combines, coordinates, or manages fare information or payments across multiple sources or services.
  • 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_69efd6b76f8c8190a7ba908aca280942 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f64e73b2408190a7e35048af465d57 completed May 2, 2026, 7:20 p.m.
PD Predicate disambiguation batch_69f64caede108190a35cc7cbfead866f completed May 2, 2026, 7:12 p.m.
Created at: April 28, 2026, 1:52 a.m.