Triple
T24162450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cruzeiro Esporte Clube (majority stake) |
E598877
|
entity |
| Predicate | clubHomeStateCompetition |
P52729
|
FINISHED |
| Object | Campeonato Mineiro |
—
|
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 Mineiro | Statement: [Cruzeiro Esporte Clube (majority stake), clubHomeStateCompetition, Campeonato Mineiro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubHomeStateCompetition Context triple: [Cruzeiro Esporte Clube (majority stake), clubHomeStateCompetition, Campeonato Mineiro]
-
A.
homeStateCompetition
chosen
Indicates a competitive event or rivalry that takes place within, or is specifically associated with, an entity’s home state.
-
B.
teamHomeState
Indicates that a team’s designated home location is within a particular state.
-
C.
homeStateTeam
Indicates that a sports team is based in, or represents, the home state of a given person or entity.
-
D.
ownedTeamHomeState
Indicates that the owning entity’s home or primary location is in the same state as the team’s home state.
-
E.
homeStateTeamOf
Indicates that one team is the designated home-state team associated with a particular person, organization, or 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:32 p.m.