Triple
T8499000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kora |
E201168
|
entity |
| Predicate | traditionallyPlayedBy |
P78239
|
FINISHED |
| Object | griots |
—
|
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: griots | Statement: [kora, traditionallyPlayedBy, griots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyPlayedBy Context triple: [kora, traditionallyPlayedBy, griots]
-
A.
isTypicallyPlayed
chosen
Indicates that an activity, game, or sport is commonly engaged in or performed by a particular type of participant or group.
-
B.
playsWith
Indicates that one entity engages in play or recreational activity together with another entity.
-
C.
playedFor
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
D.
canAlsoBePlayedIn
Indicates that something (such as a game, media, or activity) is additionally playable or usable in another context, format, or environment beyond its primary one.
-
E.
playedWith
Indicates that one entity engaged in play or a playful activity together with another entity.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5984d7481908c41c57bef9cf254 |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:14 p.m.