Triple
T27543581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EAFF |
E695300
|
entity |
| Predicate | confederationUnder |
P14830
|
FINISHED |
| Object | FIFA |
—
|
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: FIFA | Statement: [EAFF, confederationUnder, FIFA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confederationUnder Context triple: [EAFF, confederationUnder, FIFA]
-
A.
confederation
Indicates a formal union or alliance between multiple entities that retain their individual autonomy while cooperating under a shared framework or agreement.
-
B.
confederation1
Indicates a relationship where multiple entities join together in a loose alliance or union while retaining their individual autonomy.
-
C.
confederation2
Indicates a formal alliance or union in which multiple entities join together under a shared framework while retaining their individual autonomy.
-
D.
subConfederation
chosen
Indicates that one confederation is a subordinate or component part of a larger confederation within a hierarchical organizational structure.
-
E.
formerConfederation
Indicates that an entity was previously part of a confederation but is no longer a member.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 1:32 p.m.