Triple
T32864076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copa Sul-Minas-Rio |
E840598
|
entity |
| Predicate | includedClubRegion |
P53113
|
FINISHED |
| Object | clubs from South Region of Brazil |
—
|
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: clubs from South Region of Brazil | Statement: [Copa Sul-Minas-Rio, includedClubRegion, clubs from South Region of Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedClubRegion Context triple: [Copa Sul-Minas-Rio, includedClubRegion, clubs from South Region of Brazil]
-
A.
clubRegion
chosen
Indicates that a club is located in, associated with, or belongs to a particular geographic region.
-
B.
supportsClubRegion
Indicates that an entity provides backing, resources, or endorsement to a club associated with a particular geographic region.
-
C.
supportsClubContinent
Indicates that one entity provides backing, endorsement, or assistance to a club associated with a particular continent.
-
D.
includedRegions
Indicates that certain regions are contained within, or form part of, a larger specified region or set of regions.
-
E.
participantsRegion
Indicates that the related entities are associated with, originate from, or operate within a specified 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a02145017b08190bd424cc647c08d3b |
completed | May 11, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_6a021338e2b08190980c489ee44c18b3 |
completed | May 11, 2026, 5:34 p.m. |
Created at: May 1, 2026, 1:17 a.m.