Triple
T36866594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roy L. "Rocky" Dennis |
E911099
|
entity |
| Predicate | portrayedInFictionBy |
P33556
|
FINISHED |
| Object | Eric Stoltz |
E114283
|
NE 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: Eric Stoltz | Statement: [Roy L. "Rocky" Dennis, portrayedInFictionBy, Eric Stoltz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedInFictionBy Context triple: [Roy L. "Rocky" Dennis, portrayedInFictionBy, Eric Stoltz]
-
A.
appearsInFictionAs
Indicates that one entity is depicted or represented as a character, figure, or element within a fictional work or narrative.
-
B.
portrayedInAuthor
Indicates that an author is depicted or represented as a character or figure within a particular work.
-
C.
portrayedFictionalVersionOf
Indicates that one entity depicted or acted as a fictionalized or altered version of another entity.
-
D.
portraysFictionalEntity
chosen
Indicates that one entity depicts, represents, or plays the role of a fictional character or figure.
-
E.
fictionalCharacterPortrayedFromWorkBy
Indicates that a fictional character is depicted or portrayed in a work that was created by a specific author or creator.
- F. None of above.
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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dfae4007c819090d9b60a4f89bd59 |
completed | June 26, 2026, 4:07 a.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
Created at: May 3, 2026, 4:13 p.m.