Triple
T11686247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joost van der Westhuizen |
E277750
|
entity |
| Predicate | internationalPoints |
P101257
|
FINISHED |
| Object | 190 |
—
|
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: 190 | Statement: [Joost van der Westhuizen, internationalPoints, 190]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internationalPoints Context triple: [Joost van der Westhuizen, internationalPoints, 190]
-
A.
conversionPoints
Indicates a relationship where one entity defines specific points, stages, or conditions at which another entity is converted, transformed, or counted as a conversion.
-
B.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
C.
internationalUsage
Indicates that something is used or applied across multiple countries or in an international context.
-
D.
internationalContribution
Indicates that an entity provides resources, support, or participation that benefits or advances activities beyond its own country at an international level.
-
E.
betweenCountry
Indicates a relationship or interaction that involves or occurs among two or more countries.
- 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.