Triple
T29649579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poland vs Senegal (2018 FIFA World Cup) |
E756097
|
entity |
| Predicate | team1Captain |
P13597
|
FINISHED |
| Object | Robert Lewandowski |
—
|
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: Robert Lewandowski | Statement: [Poland vs Senegal (2018 FIFA World Cup), team1Captain, Robert Lewandowski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team1Captain Context triple: [Poland vs Senegal (2018 FIFA World Cup), team1Captain, Robert Lewandowski]
-
A.
teamCaptain
Indicates that one entity serves as the captain or designated leader of a particular team.
-
B.
homeTeamCaptain
chosen
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.
awayTeamCaptain
Indicates that one entity serves as the captain or designated leader of the away (visiting) team in a competition or match.
-
D.
captainedRepresentativeTeam
Indicates that an entity has served as the captain of a representative (e.g., national or regional) team.
-
E.
winningCaptain
Indicates that the subject is the captain of a team that has won a particular match, tournament, or competition.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 6:51 p.m.