Triple
T32558939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Man of Steel (additional music, with Hans Zimmer) |
E832167
|
entity |
| Predicate | forFranchise |
P76267
|
FINISHED |
| Object | Superman |
—
|
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: Superman | Statement: [Man of Steel (additional music, with Hans Zimmer), forFranchise, Superman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forFranchise Context triple: [Man of Steel (additional music, with Hans Zimmer), forFranchise, Superman]
-
A.
franchiseConnection
chosen
Indicates a relationship where one entity is part of, derived from, or otherwise officially linked to a larger franchise or brand.
-
B.
franchiseIntent
Indicates an entity’s intention or plan to establish, acquire, or operate a franchise relationship with another entity.
-
C.
franchiseOf
Indicates that one entity operates as a franchise belonging to or licensed by another entity.
-
D.
participatingFranchise
Indicates that a franchise is involved as a participant in a particular program, event, or arrangement.
-
E.
supportsFranchise
Indicates that one entity provides backing, resources, or endorsement to help establish, maintain, or promote a franchise associated with another entity.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c604600481908a261d74bdf50bee |
completed | May 3, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:03 a.m.