Triple
T33977414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Mitchell Rosenberg |
E871178
|
entity |
| Predicate | developedForFilm |
P192240
|
FINISHED |
| Object | Cowboys & Aliens |
—
|
NE NERFINISHED |
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: Cowboys & Aliens | Statement: [Scott Mitchell Rosenberg, developedForFilm, Cowboys & Aliens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedForFilm Context triple: [Scott Mitchell Rosenberg, developedForFilm, Cowboys & Aliens]
-
A.
developedForDirector
Indicates that something (such as a work, project, or product) was created or developed specifically for a particular director.
-
B.
usedInProductionOfFilm
Indicates that something (such as a resource, tool, or material) was utilized during the making or production process of a film.
-
C.
hasTypeOfUseInFilm
Indicates that something is associated with a specific manner or category of use within the context of a film.
-
D.
recordedForFilm
Indicates that an audio or performance was captured specifically for use in a film production.
-
E.
filmedFor
Indicates that something was recorded or produced specifically for a particular purpose, audience, platform, or project.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: May 1, 2026, 1:50 a.m.