Triple
T11699085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Coming Race |
E278072
|
entity |
| Predicate | hasImaginaryTechnology |
P61798
|
FINISHED |
| Object | Vril energy |
—
|
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: Vril energy | Statement: [The Coming Race, hasImaginaryTechnology, Vril energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImaginaryTechnology Context triple: [The Coming Race, hasImaginaryTechnology, Vril energy]
-
A.
hasTechnologyTheme
Indicates that something is associated with, centers on, or prominently features technology as a primary theme or subject.
-
B.
inUniverseTechnologyOf
Indicates that a technology exists within, and is part of, the fictional universe or setting associated with a given entity.
-
C.
hasImaginaryFriendCharacter
Indicates that an entity is associated with or has an imaginary friend character.
-
D.
featuresFictionalTechnology
chosen
Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
-
E.
hasImaginedIdentity
Indicates that an entity mentally constructs or adopts a non-actual identity, role, or persona for itself or another 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47df68c81908a91919a69b4880d |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.