Triple
T29877504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Star Wars Story |
E758780
|
entity |
| Predicate | usedInOnScreenTitle |
P173685
|
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, usedInOnScreenTitle, Rogue One: A Star Wars Story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInOnScreenTitle Context triple: [A Star Wars Story, usedInOnScreenTitle, Rogue One: A Star Wars Story]
-
A.
usedAsTitleOn
chosen
Indicates that something functions as a title applied to or displayed on a particular entity.
-
B.
usedTitleIn
Indicates that one entity employed or referenced another entity as a title in some context.
-
C.
usesTitleIn
Indicates that an entity is referred to using a particular title within a specified context or medium.
-
D.
usedAsTitleInFull
Indicates that something functions as a formal title within the complete, official version of a name or designation.
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 29, 2026, 5:56 p.m.