Triple
T9290250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelly Olynyk |
E223497
|
entity |
| Predicate | playsAs |
P87456
|
FINISHED |
| Object | stretch big man |
—
|
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: stretch big man | Statement: [Kelly Olynyk, playsAs, stretch big man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsAs Context triple: [Kelly Olynyk, playsAs, stretch big man]
-
A.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
B.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
C.
portraysActorAs
Indicates that one entity depicts or represents an actor in a particular role, character, or manner.
-
D.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
E.
actingRoleType
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08643a848190a8b5be1ccc0b2ef6 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:35 p.m.