Triple
T21633316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinesound Productions |
E533888
|
entity |
| Predicate | producedContentType |
P145327
|
FINISHED |
| Object | short 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: short films | Statement: [Cinesound Productions, producedContentType, short films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedContentType Context triple: [Cinesound Productions, producedContentType, short films]
-
A.
describesContentType
Indicates that one entity specifies or characterizes the type or category of content associated with another entity.
-
B.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
-
C.
governsContentType
Indicates that one entity defines or controls the rules, behavior, or handling associated with a particular content type.
-
D.
documentTypeProduced
Indicates that one entity produces, generates, or creates a document of a specified type.
-
E.
producesFor
Indicates that one entity creates, manufactures, or generates something specifically intended for another entity’s use, benefit, or distribution.
- 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52185dbc819096ad2fc5b7d953f8 |
completed | April 27, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:35 p.m.