Triple
T32560651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Eyes |
E832214
|
entity |
| Predicate | filmUniverseContext |
P84656
|
FINISHED |
| Object | Jackson Maine concert performance |
—
|
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: Jackson Maine concert performance | Statement: [Black Eyes, filmUniverseContext, Jackson Maine concert performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmUniverseContext Context triple: [Black Eyes, filmUniverseContext, Jackson Maine concert performance]
-
A.
fandomFranchise
Indicates that one entity is a fan community or fandom specifically devoted to the other entity as a franchise or media property.
-
B.
hasFictionalUniverseProperty
chosen
Indicates that a fictional universe possesses a specific characteristic, attribute, or property.
-
C.
filmSeries
Indicates that a film is part of, or associated with, a larger film series or franchise.
-
D.
franchiseUniverse
Indicates that multiple works, characters, or stories exist within and are connected by the same overarching fictional franchise or narrative universe.
-
E.
filmStudioInFiction
Indicates that a fictional work features or references a film studio within its narrative or setting.
- 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_69f6c6059f6481908d3e3ad74e5fca4d |
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.