Triple
T2953580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnificent Obsession (1954 film) |
E79877
|
entity |
| Predicate | studioSystem |
P25497
|
FINISHED |
| Object | Hollywood studio system |
—
|
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: Hollywood studio system | Statement: [Magnificent Obsession (1954 film), studioSystem, Hollywood studio system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studioSystem Context triple: [Magnificent Obsession (1954 film), studioSystem, Hollywood studio system]
-
A.
primarySystem
Indicates that one system is designated as the main or most important system in relation to another system or context.
-
B.
studioSystemFilm
chosen
Indicates that a film was produced, distributed, or otherwise created under the control or framework of a particular studio system.
-
C.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
D.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
E.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98fe4b688190a0f68c4f80cd6f8f |
completed | March 8, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.