Triple
T32827608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netherlands vs Argentina (2014 FIFA World Cup semi-final) |
E839594
|
entity |
| Predicate | teamCaptainNetherlands |
P14876
|
FINISHED |
| Object | Wesley Sneijder |
—
|
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: Wesley Sneijder | Statement: [Netherlands vs Argentina (2014 FIFA World Cup semi-final), teamCaptainNetherlands, Wesley Sneijder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamCaptainNetherlands Context triple: [Netherlands vs Argentina (2014 FIFA World Cup semi-final), teamCaptainNetherlands, Wesley Sneijder]
-
A.
countryOfNLTeam
Indicates the country that a particular national league team represents or belongs to.
-
B.
teamFromNL
Indicates that a team is associated with or originates from the National League (NL).
-
C.
captainOfGermany
Indicates that a person serves as the captain (team leader) of the Germany national team in a given context.
-
D.
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.
-
E.
teamCaptain
chosen
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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:16 a.m.