Triple
T27932641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Benteke |
E708023
|
entity |
| Predicate | FIFAElegibility |
P149218
|
FINISHED |
| Object | Belgium |
—
|
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: Belgium | Statement: [Christian Benteke, FIFAElegibility, Belgium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FIFAElegibility Context triple: [Christian Benteke, FIFAElegibility, Belgium]
-
A.
fifaEligibility
chosen
Indicates that an entity (typically a player) meets the official criteria to represent a particular national team under FIFA regulations.
-
B.
fifaEligibilityRule
Indicates that a person meets the official criteria set by FIFA to represent a particular national team in international football competitions.
-
C.
fifaMembership
Indicates that an entity is a member association or organization officially affiliated with FIFA.
-
D.
fifaApproved
Indicates that something has been officially recognized, certified, or sanctioned by FIFA according to its standards or regulations.
-
E.
fifaRecognized
Indicates that an organization, competition, or entity is officially recognized or sanctioned by FIFA as meeting its standards or falling under its authority.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:03 p.m.