Triple
T9006015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eric Owens |
E215144
|
entity |
| Predicate | hasPerformedRole |
P36975
|
FINISHED |
| Object | Porgy in Porgy and Bess |
—
|
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: Porgy in Porgy and Bess | Statement: [Eric Owens, hasPerformedRole, Porgy in Porgy and Bess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformedRole Context triple: [Eric Owens, hasPerformedRole, Porgy in Porgy and Bess]
-
A.
hasPlayedRole
chosen
Indicates that an entity has performed or portrayed a particular role or character in some context (such as a film, play, or production).
-
B.
hasHistoricalRoleAs
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
-
C.
mayHavePriorRole
Indicates that an entity is allowed or expected to have held a specified role at some earlier time.
-
D.
hasBelovedRole
Indicates that an entity holds a role or position that is deeply cherished or loved by another entity.
-
E.
hasProductionRole
Indicates that an entity holds a specific role or function in the production or creation process of 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc69bc6e208190b0c01e3761c04799 |
completed | April 1, 2026, 12:41 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.