Triple
T17663342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA World Cup Golden Ball 1986 |
E440306
|
entity |
| Predicate | winnerCaptaincy |
P19291
|
FINISHED |
| Object | captain of Argentina national team |
—
|
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: captain of Argentina national team | Statement: [FIFA World Cup Golden Ball 1986, winnerCaptaincy, captain of Argentina national team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerCaptaincy Context triple: [FIFA World Cup Golden Ball 1986, winnerCaptaincy, captain of Argentina national team]
-
A.
winningCaptain
chosen
Indicates that the subject is the captain of a team that has won a particular match, tournament, or competition.
-
B.
homeTeamCaptain
Indicates that one entity serves as the captain of the home team in a given game or match in relation to the other entity.
-
C.
wicketKeeperCaptain
Indicates that the subject serves simultaneously as both the wicket-keeper and the captain for a cricket team.
-
D.
captainedRepresentativeTeam
Indicates that an entity has served as the captain of a representative (e.g., national or regional) team.
-
E.
teamCaptain
Indicates that one entity serves as the captain or designated leader of a particular team.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea7f0ec81908eff43aa845584af |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:51 a.m.