Triple
T33040022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juror 8 |
E845433
|
entity |
| Predicate | appearsInTeleplay |
P795
|
FINISHED |
| Object | 12 Angry Men (1954 teleplay) |
—
|
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: 12 Angry Men (1954 teleplay) | Statement: [Juror 8, appearsInTeleplay, 12 Angry Men (1954 teleplay)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInTeleplay Context triple: [Juror 8, appearsInTeleplay, 12 Angry Men (1954 teleplay)]
-
A.
episodeTeleplayBy
Indicates that a specific episode’s teleplay (script for television) was written by a particular person.
-
B.
appearsInScriptType
Indicates that an entity is featured or occurs within a script of a specified type or category.
-
C.
appearsInAdaptationBy
Indicates that an entity is featured or present in an adaptation created by a specified adapter (e.g., author, director, or studio).
-
D.
appearsWithActor
Indicates that one entity appears together on screen or in a scene with a specified actor.
-
E.
appearsIn
chosen
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 1, 2026, 1:24 a.m.