Triple
T29253631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Backlot |
E741636
|
entity |
| Predicate | mediaFranchiseRepresentation |
P170420
|
FINISHED |
| Object | Aerosmith |
—
|
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: Aerosmith | Statement: [Backlot, mediaFranchiseRepresentation, Aerosmith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaFranchiseRepresentation Context triple: [Backlot, mediaFranchiseRepresentation, Aerosmith]
-
A.
mediaFranchiseDerivedFrom
Indicates that one media franchise originates from, is based on, or was developed from another pre-existing work or franchise.
-
B.
mediaFranchiseType
Indicates the specific kind or category of media franchise that an entity belongs to (e.g., film series, TV franchise, game franchise).
-
C.
fandomFranchise
Indicates that one entity is a fan community or fandom specifically devoted to the other entity as a franchise or media property.
-
D.
hasMediaFranchise
Indicates that one entity is part of, or belongs to, a larger media franchise represented by another entity.
-
E.
fandomScope
Indicates the extent or boundaries of a fandom-related relationship, such as how broadly or narrowly a fan’s interest, participation, or recognition applies.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 28, 2026, 12:35 p.m.