Triple
T23660655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zanuck Independent |
E584434
|
entity |
| Predicate | roleInTheZeroTheorem |
P152898
|
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: [Zanuck Independent, roleInTheZeroTheorem, producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTheZeroTheorem Context triple: [Zanuck Independent, roleInTheZeroTheorem, producer]
-
A.
roleInTheory
Indicates the specific function, position, or contribution that an entity has within a particular theory or theoretical framework.
-
B.
roleInTranscendence
Indicates that an entity plays a specific role or function in another entity’s process, state, or act of transcendence.
-
C.
roleInElysium
Indicates that an entity holds a specific role, position, or function within the context of Elysium.
-
D.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
-
E.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
- F. None of above. chosen
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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35f03448190834991c2a65ef0e4 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:50 p.m.