Triple
T36974501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dale Steyn |
E914660
|
entity |
| Predicate | testCapNumberForSouthAfrica |
P186830
|
FINISHED |
| Object | 300 |
—
|
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: 300 | Statement: [Dale Steyn, testCapNumberForSouthAfrica, 300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testCapNumberForSouthAfrica Context triple: [Dale Steyn, testCapNumberForSouthAfrica, 300]
-
A.
testCapNumberForIndia
Indicates that an entity’s capital number or capitalization value is being tested or validated specifically for India.
-
B.
testCapNumberForSriLanka
Indicates performing a validation check on whether a given number conforms to the specific CAP numbering rules used in Sri Lanka.
-
C.
testCapNumberForEngland
Indicates that an entity’s cap number is being checked or validated specifically for England.
-
D.
testCapNumberForWestIndies
Indicates the assigned cap number used to identify a player who has represented the West Indies cricket team.
-
E.
t20iCapNumber
Indicates that an entity has a specific cap number (e.g., a player’s official cap or appearance number) assigned to it.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:14 p.m.