Triple
T29191151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Icarus Agenda |
E739993
|
entity |
| Predicate | hasFictionalGenreCategory |
P116833
|
FINISHED |
| Object | 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: spy fiction | Statement: [The Icarus Agenda, hasFictionalGenreCategory, spy fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalGenreCategory Context triple: [The Icarus Agenda, hasFictionalGenreCategory, spy fiction]
-
A.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
B.
hasFictionalUniverseGenre
Indicates that a fictional universe is associated with a particular genre that characterizes its overall style, themes, or narrative type.
-
C.
hasGenreInFiction
chosen
Indicates that a work of fiction belongs to or is categorized under a specific literary genre.
-
D.
hasFictionalProductionType
Indicates that an entity is associated with a specific type or category of fictional production (such as a genre, format, or style).
-
E.
hasFictionalGenreCycle
Indicates a recurring or cyclical pattern that characterizes the fictional genre associated with an entity.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 28, 2026, 12:02 p.m.