Triple
T24417569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FWA Footballer of the Year 2016–17 |
E615628
|
entity |
| Predicate | previousAward |
P91278
|
FINISHED |
| Object | FWA Footballer of the Year 2015–16 |
—
|
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: FWA Footballer of the Year 2015–16 | Statement: [FWA Footballer of the Year 2016–17, previousAward, FWA Footballer of the Year 2015–16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAward Context triple: [FWA Footballer of the Year 2016–17, previousAward, FWA Footballer of the Year 2015–16]
-
A.
predecessorAward
chosen
Indicates that one award directly preceded another award in sequence or succession.
-
B.
receivedAwardIn
Indicates that an entity was given or obtained a specific award in a particular place or context.
-
C.
awardReceived
Indicates that an entity has been granted or honored with a specific award or recognition.
-
D.
awardConferred
Indicates that an award or honor has been formally granted by one entity to another.
-
E.
formerlyAwardedIn
Indicates that an award or recognition was previously given in a particular context, time, or location but is no longer awarded there.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29587b2308190907886b82d8c5129 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:13 a.m.