Triple
T5662107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA vice president |
E124766
|
entity |
| Predicate | rangeOfInfluence |
P2828
|
FINISHED |
| Object | member associations of FIFA |
—
|
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: member associations of FIFA | Statement: [FIFA vice president, rangeOfInfluence, member associations of FIFA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeOfInfluence Context triple: [FIFA vice president, rangeOfInfluence, member associations of FIFA]
-
A.
sphereOfInfluence
chosen
Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
-
B.
typeOfInfluence
Indicates the specific nature or category of influence that one entity exerts on another.
-
C.
affectedArea
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
D.
influencesRegion
Indicates that one entity has an effect on, shapes, or alters the conditions, characteristics, or behavior of a specified region.
-
E.
hasBoundaryInfluenceFrom
Indicates that the boundary or limits of one entity are affected, shaped, or determined by another entity.
- 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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:42 p.m.