Triple
T30821467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Man film series |
E784931
|
entity |
| Predicate | createdByStudioFranchise |
P196588
|
FINISHED |
| Object | Marvel Studios |
—
|
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: Marvel Studios | Statement: [Iron Man film series, createdByStudioFranchise, Marvel Studios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdByStudioFranchise Context triple: [Iron Man film series, createdByStudioFranchise, Marvel Studios]
-
A.
createdForFranchise
Indicates that something was created specifically to belong to, support, or be used within a particular franchise.
-
B.
producedForStudio
Indicates that a work (such as a film, show, or recording) was created under contract for, and on behalf of, a particular studio.
-
C.
introducedByStudio
Indicates that a work, product, or project was initially presented, launched, or brought to public attention by a particular studio.
-
D.
coCreatedFranchiseWith
Indicates that two or more entities jointly created or originated the same franchise.
-
E.
formedByFranchise
Indicates that something (such as a team, organization, or unit) was created or established as a result of a franchise agreement or franchising process.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
| PDg | Predicate description generation | batch_69fe5d580d7c819097cb18d438b01d08 |
completed | May 8, 2026, 10:02 p.m. |
Created at: April 29, 2026, 8:44 p.m.