Triple
T27157585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gizmodo |
E682562
|
entity |
| Predicate | io9Focus |
P161921
|
FINISHED |
| Object | futurism |
—
|
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: futurism | Statement: [Gizmodo, io9Focus, futurism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: io9Focus Context triple: [Gizmodo, io9Focus, futurism]
-
A.
io9Focus
chosen
Indicates a primary emphasis or central attention directed toward the subject within the io9-related context.
-
B.
fandomFocus
Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
-
C.
comicBookUniverse
Indicates that multiple comic book characters, stories, or events exist within and are governed by the same fictional continuity or shared narrative world.
-
D.
fandomScope
Indicates the extent or boundaries of a fandom-related relationship, such as how broadly or narrowly a fan’s interest, participation, or recognition applies.
-
E.
fanCultureElement
Indicates a relationship where something is a notable practice, artifact, or tradition that characterizes or expresses a particular fan culture.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62508724481909a30255975def6e3 |
completed | May 2, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:17 a.m.