Triple
T38570042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleaver |
E929239
|
entity |
| Predicate | producerInUniverse |
P27679
|
FINISHED |
| Object | Christopher Moltisanti |
—
|
NE NERFINISHED |
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: Christopher Moltisanti | Statement: [Cleaver, producerInUniverse, Christopher Moltisanti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producerInUniverse Context triple: [Cleaver, producerInUniverse, Christopher Moltisanti]
-
A.
createdInUniverseBy
Indicates that something was brought into existence within a particular fictional or conceptual universe by a specific creator or originating agent.
-
B.
producerCharacter
Indicates that a producer is responsible for or associated with a particular character in a work.
-
C.
producerInFiction
chosen
Indicates that an entity serves as a producer (e.g., of a show, film, or other work) within a fictional context or narrative.
-
D.
producerRole
Indicates that an entity serves in the role of producer for another entity, such as a work, product, or event.
-
E.
producerOfWork
Indicates that one entity is the creator or originator responsible for producing a particular work.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: May 3, 2026, 4:32 p.m.