Triple
T28074182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Generation (Belgium national football team) |
E709486
|
entity |
| Predicate | keyCaptain |
P884
|
FINISHED |
| Object | Eden Hazard |
—
|
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: Eden Hazard | Statement: [Golden Generation (Belgium national football team), keyCaptain, Eden Hazard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyCaptain Context triple: [Golden Generation (Belgium national football team), keyCaptain, Eden Hazard]
-
A.
captain
chosen
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
-
B.
assistantCaptain
Indicates that one entity serves as the assistant or deputy to another entity who holds the role of captain.
-
C.
laterCaptain
Indicates that one entity becomes the captain of something at a later time than another referenced captain or captaincy.
-
D.
coCaptain
Indicates that two or more individuals share the role and responsibilities of captain jointly.
-
E.
losingCaptain
Indicates that the referenced captain is the one who lost in a particular contest, game, or competitive event.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6403e306081909e463520c0ae7437 |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:48 p.m.