Triple
T37041826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quinton de Kock |
E916798
|
entity |
| Predicate | hasCaptaincyExperience |
P143873
|
FINISHED |
| Object | South Africa ODI team |
—
|
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: South Africa ODI team | Statement: [Quinton de Kock, hasCaptaincyExperience, South Africa ODI team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaptaincyExperience Context triple: [Quinton de Kock, hasCaptaincyExperience, South Africa ODI team]
-
A.
hasCaptainsFormatParticipation
chosen
Indicates that an entity participates in a competition, event, or context specifically in the role or format of a captain.
-
B.
servedAsCaptainFrom
Indicates that an entity held the role of captain of another entity starting from a specified point in time.
-
C.
yearsAsCaptainEnd
Indicates the point in time or year when an entity’s tenure or period of serving as captain ends.
-
D.
hasNotableCaptain
Indicates that an entity has a specific captain who is recognized as notable or distinguished in some way.
-
E.
hasLeadershipExperienceIn
Indicates that an entity possesses prior leadership experience specifically within a given domain, context, or organization.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
Created at: May 3, 2026, 4:14 p.m.