Triple
T5637305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Film i Väst |
E100278
|
entity |
| Predicate | hasCoProduced |
P24872
|
FINISHED |
| Object | European arthouse films |
—
|
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: European arthouse films | Statement: [Film i Väst, hasCoProduced, European arthouse films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoProduced Context triple: [Film i Väst, hasCoProduced, European arthouse films]
-
A.
coProduced
chosen
Indicates that two or more entities jointly produced or created a work, project, or product together.
-
B.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
C.
coDirectedWith
Indicates that two or more entities jointly directed the same work or project.
-
D.
associatedProduction
Indicates that there is a related or connected production (such as a work, performance, or manufacturing process) linked to the subject entity.
-
E.
executiveProducerOf
Indicates that one entity serves as the executive producer responsible for overseeing the creation or production of another entity, such as a film, series, or other media work.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022820b7c81908f79c0a124d6b940 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.