Triple
T10821219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebula Award for Best Script |
E255373
|
entity |
| Predicate | award for dramatic presentation in speculative fiction media |
P95920
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nebula Award for Best Script, award for dramatic presentation in speculative fiction media, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: award for dramatic presentation in speculative fiction media Context triple: [Nebula Award for Best Script, award for dramatic presentation in speculative fiction media, true]
-
A.
awardWithinFiction
Indicates that an award is given or exists within a fictional context or narrative world, rather than in real life.
-
B.
awardInStoryline
Indicates that an award is given to a character or entity within the context of a specific narrative or storyline.
-
C.
adaptationAward
Indicates that an entity has received an award specifically for its adaptation of another work.
-
D.
awardMedium
Indicates the medium or format through which an award is given, presented, or communicated.
-
E.
awardGivenBy
Indicates that an award is conferred or presented by one entity to another.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344ae2688190bceabf41c79d298d |
completed | April 9, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:18 p.m.