Triple
T29613478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Garden of Weapons (Herbie Kruger) |
E754795
|
entity |
| Predicate | workInTheGenreOf |
P14417
|
FINISHED |
| Object | British spy fiction |
—
|
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: British spy fiction | Statement: [The Garden of Weapons (Herbie Kruger), workInTheGenreOf, British spy fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInTheGenreOf Context triple: [The Garden of Weapons (Herbie Kruger), workInTheGenreOf, British spy fiction]
-
A.
workedOnGenre
chosen
Indicates that an entity (such as a person or organization) has done work related to a particular genre.
-
B.
hasGenreOfWorkItAppearsIn
Indicates that an entity is associated with the genre of the work in which it appears.
-
C.
genreOfWorkDescribedIn
Indicates that a work is characterized as belonging to a particular genre as described in another resource or context.
-
D.
basedOnWorkGenre
Indicates that one entity’s genre classification is derived from or determined by the genre of another work.
-
E.
genreOfWorkPerformedIn
Indicates that a specified genre characterizes the type of work that is performed in a particular event, context, or setting.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e1e5c5c81909acf808419a9e48f |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:30 p.m.