Triple
T32864025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federação Paulista de Futebol |
E840596
|
entity |
| Predicate | subsidiaryOrBranchOf |
P71890
|
FINISHED |
| Object | Confederação Brasileira de Futebol |
—
|
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: Confederação Brasileira de Futebol | Statement: [Federação Paulista de Futebol, subsidiaryOrBranchOf, Confederação Brasileira de Futebol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsidiaryOrBranchOf Context triple: [Federação Paulista de Futebol, subsidiaryOrBranchOf, Confederação Brasileira de Futebol]
-
A.
usedBySubsidiaryOf
Indicates that something is used by an entity that is a subsidiary of another organization.
-
B.
coreSubsidiaryOf
chosen
Indicates that one entity is a primary or central subsidiary that is owned or controlled by another entity.
-
C.
subsidiaryOrAsset
Indicates that one entity is owned, controlled, or held as a subsidiary company or asset by another entity.
-
D.
hasSubsidiaryLabel
Indicates that one entity is identified as a subsidiary or subordinate organization of another entity.
-
E.
hasSubsidiaryBusiness
Indicates that one business entity owns or controls another business entity as its subsidiary.
- 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_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:17 a.m.