Triple
T13538433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World 11 |
E323319
|
entity |
| Predicate | usesVotingBallots |
P110753
|
FINISHED |
| Object | FIFPro member players |
—
|
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: FIFPro member players | Statement: [World 11, usesVotingBallots, FIFPro member players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVotingBallots Context triple: [World 11, usesVotingBallots, FIFPro member players]
-
A.
usesVotingBody
Indicates that one entity employs or relies on a particular voting body to make decisions or take actions on its behalf.
-
B.
usesVotingDiscipline
Indicates that an entity follows or enforces a coordinated pattern of voting behavior, typically aligning votes according to a shared strategy, rule, or group directive.
-
C.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
D.
usesVoterLists
Indicates that one entity employs or relies on voter registration lists in relation to another entity or activity.
-
E.
numberOfBallots
Indicates the total count of ballots associated with a particular election, contest, or voting event.
- F. None of above. chosen
Provenance (4 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafd7ad9481908fe1d7ffcf8fab71 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:45 p.m.