Triple
T32173991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crossing 2 |
E821785
|
entity |
| Predicate | directorStyleDescribedAs |
P110214
|
FINISHED |
| Object | operatic |
—
|
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: operatic | Statement: [The Crossing 2, directorStyleDescribedAs, operatic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorStyleDescribedAs Context triple: [The Crossing 2, directorStyleDescribedAs, operatic]
-
A.
directedInStyle
Indicates that a work was directed in a particular stylistic manner or according to a specific directing style.
-
B.
directorialStyle
chosen
Indicates the characteristic manner or approach a director consistently uses in creating and shaping their works.
-
C.
playsInStyleOf
Indicates that one entity performs, creates, or behaves in a manner characteristic of another entity’s style.
-
D.
inTheStyleOf
Indicates that one entity is created, performed, or presented in a manner that imitates or closely resembles the characteristic style of another entity.
-
E.
directorDescribedAs
Indicates that a director is characterized or portrayed using a particular description, label, or set of attributes.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 1, 2026, 12:34 a.m.