Triple
T29906287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castelão |
E759542
|
entity |
| Predicate | meetsFIFAStandards |
P40884
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Castelão, meetsFIFAStandards, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsFIFAStandards Context triple: [Castelão, meetsFIFAStandards, yes]
-
A.
fifaApproved
chosen
Indicates that something has been officially recognized, certified, or sanctioned by FIFA according to its standards or regulations.
-
B.
fifaEligibility
Indicates that an entity (typically a player) meets the official criteria to represent a particular national team under FIFA regulations.
-
C.
fifaEligibilityRule
Indicates that a person meets the official criteria set by FIFA to represent a particular national team in international football competitions.
-
D.
fifaRecognized
Indicates that an organization, competition, or entity is officially recognized or sanctioned by FIFA as meeting its standards or falling under its authority.
-
E.
fifaWorldCupOfficialMatchBallFor
Indicates that something is the officially designated match ball used for a specific FIFA World Cup tournament or match.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67756337881908627f7068dc02d9f |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:08 p.m.