Triple
T32864061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campeonato dos Campeões (1937) |
E840597
|
entity |
| Predicate | involvedRegions |
P285
|
FINISHED |
| Object | different regions 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: different regions of Brazil | Statement: [Campeonato dos Campeões (1937), involvedRegions, different regions of Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedRegions Context triple: [Campeonato dos Campeões (1937), involvedRegions, different regions of Brazil]
-
A.
includedRegions
Indicates that certain regions are contained within, or form part of, a larger specified region or set of regions.
-
B.
hasRegion
chosen
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
C.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
D.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
E.
exportRegion
Indicates the region or geographic area from which goods, services, or resources are exported.
- 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_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 1, 2026, 1:17 a.m.