Triple
T29266649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clássico Vovô |
E741993
|
entity |
| Predicate | mainCompetitions |
P179490
|
FINISHED |
| Object | Campeonato Carioca |
—
|
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 Carioca | Statement: [Clássico Vovô, mainCompetitions, Campeonato Carioca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCompetitions Context triple: [Clássico Vovô, mainCompetitions, Campeonato Carioca]
-
A.
currentCompetition
Indicates that two or more entities are presently engaged in the same ongoing competition or contest.
-
B.
featuredCompetition
Indicates that a particular competition is highlighted or given special prominence relative to others.
-
C.
featuredCompetitionFor
Indicates that one entity is highlighted or promoted as a notable or primary competition associated with another entity.
-
D.
primaryCompetition
Indicates that one entity is the main or most significant competitor of another within a given market, domain, or context.
-
E.
primaryCompetitionHosted
Indicates that an entity serves as the main host or organizer of a particular competition or contest.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 28, 2026, 12:45 p.m.