Triple
T27546287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA statutory bodies |
E695370
|
entity |
| Predicate | topLegislativeBody |
P97852
|
FINISHED |
| Object | FIFA Congress |
—
|
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 Congress | Statement: [FIFA statutory bodies, topLegislativeBody, FIFA Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLegislativeBody Context triple: [FIFA statutory bodies, topLegislativeBody, FIFA Congress]
-
A.
legislativeBodyOf
Indicates that one entity is the official legislative body (lawmaking assembly) of another entity, typically a political unit such as a country, state, or city.
-
B.
legislativeBodyMemberOf
Indicates that an individual serves as a member of a specified legislative body or assembly.
-
C.
isLegislativeBody
chosen
Indicates that the subject entity functions as an official law-making or legislative body within a political or organizational system.
-
D.
formerLegislatureChambers
Indicates that an entity once served as a legislative chamber but no longer holds that function.
-
E.
previousLegislativeBody
Indicates that one legislative body directly preceded another in an official sequence or succession.
- 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_69f62f850d148190929315018576b731 |
completed | May 2, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:33 p.m.