Triple
T29266849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campeonato Brasileiro Série D |
E741998
|
entity |
| Predicate | hasClubsFrom |
P67577
|
FINISHED |
| Object | North Region of Brazil |
—
|
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: North Region of Brazil | Statement: [Campeonato Brasileiro Série D, hasClubsFrom, North Region of Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClubsFrom Context triple: [Campeonato Brasileiro Série D, hasClubsFrom, North Region of Brazil]
-
A.
participatingClubsFrom
chosen
Indicates that certain clubs are taking part in or are involved in an event, activity, or context originating from a specified source or organizer.
-
B.
hasClub
Indicates that an entity is associated with or belongs to a particular club.
-
C.
hasSportsClubs
Indicates that an entity possesses, hosts, or is associated with one or more sports clubs.
-
D.
hadMemberClubsIn
Indicates that an organization or group possessed member clubs located within a specified place or jurisdiction.
-
E.
hasInvitedClubsFrom
Indicates that a party has extended invitations to clubs originating from a specified source or location.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 28, 2026, 12:45 p.m.