Triple
T11387474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illudium Q-36 Explosive Space Modulator |
E269746
|
entity |
| Predicate | fictionalTechnologyType |
P1482
|
FINISHED |
| Object | space weapon |
—
|
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: space weapon | Statement: [Illudium Q-36 Explosive Space Modulator, fictionalTechnologyType, space weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalTechnologyType Context triple: [Illudium Q-36 Explosive Space Modulator, fictionalTechnologyType, space weapon]
-
A.
featuresFictionalTechnology
Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
-
B.
technologyType
chosen
Indicates the specific kind or category of technology associated with an entity or relationship.
-
C.
fictionalObject
Indicates that one entity is a fictional or imaginary object in relation to another entity.
-
D.
envisionedTechnology
Indicates that an entity has imagined, conceptualized, or planned a particular technology, typically before it exists or is realized.
-
E.
technicalType
Indicates the specific technical category or classification that characterizes how something is implemented, structured, or functions.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.