Triple
T32030148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Proud and Profane |
E817932
|
entity |
| Predicate | productionStudioSystemEra |
P185299
|
FINISHED |
| Object | Hollywood studio system |
—
|
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: Hollywood studio system | Statement: [The Proud and Profane, productionStudioSystemEra, Hollywood studio system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionStudioSystemEra Context triple: [The Proud and Profane, productionStudioSystemEra, Hollywood studio system]
-
A.
filmStudioEra
Indicates the historical period or era during which a particular film studio was active or most influential.
-
B.
associatedProductionEra
Indicates a relationship where something is linked to the specific time period or era during which it was produced or created.
-
C.
belongsToStudioEra
chosen
Indicates that a film or work was produced during the historical period dominated by the traditional studio system.
-
D.
producedForStudio
Indicates that a work (such as a film, show, or recording) was created under contract for, and on behalf of, a particular studio.
-
E.
producedAtStudio
Indicates that a creative work was made or recorded at a specific studio location.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 1, 2026, 12:18 a.m.