Triple
T36992283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darren Sammy |
E915136
|
entity |
| Predicate | formatCaptained |
P68557
|
FINISHED |
| Object | Twenty20 International |
—
|
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: Twenty20 International | Statement: [Darren Sammy, formatCaptained, Twenty20 International]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatCaptained Context triple: [Darren Sammy, formatCaptained, Twenty20 International]
-
A.
captainedFormat
chosen
Indicates that one entity served as the captain or leader in charge of another entity, typically a team, vessel, or organized group, during a specific event or period.
-
B.
captaincyFormat
Indicates the specific structure or style in which a captaincy role or tenure is represented or recorded.
-
C.
captainsFormatDescription
Indicates that an entity serves as the captain or leader responsible for overseeing, managing, or representing a particular format (such as a team, mode, or structured context).
-
D.
captainInName
Indicates that an entity’s name or title explicitly includes the word “Captain.”
-
E.
captaincyStyle
Indicates the manner or approach with which an individual leads or commands a team or group as its captain.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.