Triple

T32046969
Position Surface form Disambiguated ID Type / Status
Subject Paysandu Sport Club E818376 entity
Predicate mainCompetitionRegional P179490 FINISHED
Object Campeonato Paraense 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: Campeonato Paraense | Statement: [Paysandu Sport Club, mainCompetitionRegional, Campeonato Paraense]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mainCompetitionRegional
Context triple: [Paysandu Sport Club, mainCompetitionRegional, Campeonato Paraense]
  • A. regionalCompetitionParticipation
    Indicates that an entity takes part in a competition or contest organized at a regional level.
  • B. mainCompetitions chosen
    Indicates the primary contests, tournaments, or competitive events in which an entity regularly participates or is chiefly involved.
  • C. representsInRegionalCompetition
    Indicates that an entity serves as a representative of another entity in a regional-level competition or contest.
  • D. regionTournament
    Indicates a tournament that is held within, or associated with, a specific geographic or administrative region.
  • E. plannedCompetitionZone
    Indicates that a specific area has been designated in advance as the location where a competition or contest is intended to take place.
  • 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_69f348fcfb648190859f6be5e04b7cfe completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fba78aca4c8190b8f1831e8cc04e06 completed May 6, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69fba34a65a4819088bac6c17542d71c completed May 6, 2026, 8:23 p.m.
Created at: May 1, 2026, 12:20 a.m.