Triple
T9846660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contempt |
E239356
|
entity |
| Predicate | metaFilmAbout |
P90339
|
FINISHED |
| Object | adaptation of The Odyssey |
—
|
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: adaptation of The Odyssey | Statement: [Contempt, metaFilmAbout, adaptation of The Odyssey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metaFilmAbout Context triple: [Contempt, metaFilmAbout, adaptation of The Odyssey]
-
A.
filmicFunction
Indicates the role or purpose that something serves within the structure, style, or narrative function of a film.
-
B.
backedFilm
Indicates that one entity provided financial or promotional support for the production or distribution of a film.
-
C.
filmStudioInFiction
Indicates that a fictional work features or references a film studio within its narrative or setting.
-
D.
filmOrganization
Indicates a relationship where an organization is involved with a film, such as producing, distributing, or otherwise being officially associated with it.
-
E.
filmBase
Indicates the primary location or headquarters from which a film-related entity (such as a production, company, or operation) is based or operates.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb36156308190b26892702f3b41e0 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06ace53081909b5f81f382f6591e |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:34 p.m.