Triple
T33630462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julie Lockhart |
E861540
|
entity |
| Predicate | roleInRon's Gone Wrong |
P120250
|
FINISHED |
| Object | producer |
—
|
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: producer | Statement: [Julie Lockhart, roleInRon's Gone Wrong, producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRon's Gone Wrong Context triple: [Julie Lockhart, roleInRon's Gone Wrong, producer]
-
A.
theaterRole
Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
-
B.
roleInMonstersInc
Indicates the specific function, position, or part an entity has within the context of the movie “Monsters, Inc.”
-
C.
entertainmentRole
chosen
Indicates that an entity holds a specific function or position within an entertainment context (such as a role in a performance, production, or media work).
-
D.
roleInAGoofyMovie
Indicates that an entity has a role or part in the production "A Goofy Movie."
-
E.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a008e29f76881908e656dbbd7fceea3 |
completed | May 10, 2026, 1:54 p.m. |
| PD | Predicate disambiguation | batch_6a008dc01b308190bc26e69814692f82 |
completed | May 10, 2026, 1:53 p.m. |
Created at: May 1, 2026, 1:41 a.m.