Triple
T18570020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaminda Vaas |
E453848
|
entity |
| Predicate | coachedRole |
P132604
|
FINISHED |
| Object | fast bowling coach |
—
|
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: fast bowling coach | Statement: [Chaminda Vaas, coachedRole, fast bowling coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachedRole Context triple: [Chaminda Vaas, coachedRole, fast bowling coach]
-
A.
coachedAlongside
Indicates that two or more individuals served as coaches at the same time, typically for the same team, organization, or event.
-
B.
coachedFrom
Indicates that one entity served as a coach or trainer for another entity during a specified period or context.
-
C.
coachedStarPlayer
Indicates that one entity served as the coach or trainer of another entity who is considered a star player.
-
D.
conferenceCoach
Indicates a person who provides guidance, training, or mentorship to participants in the context of a conference or similar professional gathering.
-
E.
gameCoached
Indicates that one entity served as the coach for another entity in the context of a specific game or match.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b01331c8190bec3aba40358a843 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:43 a.m.