Triple
T19662581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Purvis |
E472117
|
entity |
| Predicate | hasThemeInStories |
P76865
|
FINISHED |
| Object | speculative technology |
—
|
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: speculative technology | Statement: [Harry Purvis, hasThemeInStories, speculative technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThemeInStories Context triple: [Harry Purvis, hasThemeInStories, speculative technology]
-
A.
hasThemeInStory
chosen
Indicates that a particular theme is present or plays a significant role within a given story.
-
B.
hasPersonalThemes
Indicates that something (such as a work, message, or expression) involves themes that are personal, intimate, or directly related to an individual’s own experiences or inner life.
-
C.
hasThemeType
Indicates that something is associated with or characterized by a particular thematic category or type.
-
D.
followsTheme
Indicates that one entity adheres to, is guided by, or is structured according to the theme established by another entity.
-
E.
hasSayingTheme
Indicates that a saying, proverb, or quoted expression is about or centers on a particular theme or subject.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6414b30fc81908e6594ba8f2d2942 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.