Triple
T29877502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Star Wars Story |
E758780
|
entity |
| Predicate | usedOnPosters |
P101201
|
FINISHED |
| Object | Rogue One: A Star Wars Story |
—
|
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: Rogue One: A Star Wars Story | Statement: [A Star Wars Story, usedOnPosters, Rogue One: A Star Wars Story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnPosters Context triple: [A Star Wars Story, usedOnPosters, Rogue One: A Star Wars Story]
-
A.
usedOnFront
Indicates that something is applied, displayed, or positioned on the front side or front-facing part of another object or entity.
-
B.
hasFilmPoster
Indicates that one entity serves as the film poster associated with another film entity.
-
C.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
D.
usedInMarketingMaterials
chosen
Indicates that something is included or featured as part of marketing or promotional materials.
-
E.
usedInMediaAs
Indicates that something is employed, featured, or referenced within a media work (such as a film, show, game, or publication) in some capacity.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676caee048190952d49763046a768 |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:56 p.m.