Triple
T11686248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joost van der Westhuizen |
E277750
|
entity |
| Predicate | triesForNationalTeam |
P101258
|
FINISHED |
| Object | 38 |
—
|
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: 38 | Statement: [Joost van der Westhuizen, triesForNationalTeam, 38]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triesForNationalTeam Context triple: [Joost van der Westhuizen, triesForNationalTeam, 38]
-
A.
hasPlayedForNationalTeam
Indicates that an athlete has been a member of and appeared in competition for a specified national team.
-
B.
associatedWithNationalTeam
Indicates that an entity has a formal connection or involvement with a specific national team, such as playing for, coaching, or otherwise being officially linked to it.
-
C.
includesNationalTeam
Indicates that an entity’s composition or membership list contains a specified national team.
-
D.
supportsNationalTeam
Indicates that one entity provides backing, endorsement, or assistance to a national team.
-
E.
playedForNationalTeamFrom
Indicates that an entity was a member of and played for a particular national team starting from a specified date or time period.
- F. None of above. chosen
Provenance (4 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4654be881909bd0256cf18e25de |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d89546a8688190b51455b5e12caf91 |
completed | April 10, 2026, 6:14 a.m. |
Created at: April 8, 2026, 9:40 p.m.