Triple
T32084875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clube do Remo |
E819410
|
entity |
| Predicate | homeRegionCompetition |
P15896
|
FINISHED |
| Object | Campeonato Paraense de Futebol |
—
|
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: Campeonato Paraense de Futebol | Statement: [Clube do Remo, homeRegionCompetition, Campeonato Paraense de Futebol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeRegionCompetition Context triple: [Clube do Remo, homeRegionCompetition, Campeonato Paraense de Futebol]
-
A.
homeRegionLeague
chosen
Indicates that a league is the primary or native regional competition associated with an entity (such as a team or club).
-
B.
homeStateCompetition
Indicates a competitive event or rivalry that takes place within, or is specifically associated with, an entity’s home state.
-
C.
regionalCompetitionParticipation
Indicates that an entity takes part in a competition or contest organized at a regional level.
-
D.
homeCompetitionZone
Indicates that a competition or event takes place in the home zone or home territory associated with a particular participant or entity.
-
E.
clubRegion
Indicates that a club is located in, associated with, or belongs to a particular geographic region.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:24 a.m.