Triple
T18946019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legacy of the Force |
E463515
|
entity |
| Predicate | hasBook |
P29317
|
FINISHED |
| Object | Fury |
—
|
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: Fury | Statement: [Legacy of the Force, hasBook, Fury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fury Context triple: [Legacy of the Force, hasBook, Fury]
-
A.
Fury
"Fury" is an episode of Star Trek: Voyager that focuses on the return of the Ocampa woman Kes in a darker, more vengeful role.
-
B.
Fury
chosen
Fury is a novel by Salman Rushdie that explores themes of identity, rage, and dislocation through the story of an Indian-born academic living in New York City.
-
C.
Fury
Fury is the nickname of Ottawa Fury FC, a professional soccer club based in Ottawa, Canada.
-
D.
Fury
Fury is a classic science fiction novel by Henry Kuttner, set on a post-apocalyptic Venus and known for its exploration of power, mutation, and human society.
-
E.
Fury
Fury is a mythological avenging spirit, one of the Furies (Erinyes) from Greek and Roman mythology, who personifies vengeance and retribution.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d53f6eb8819099b1268db8b14d66 |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 10, 2026, 11:59 a.m.