Triple
T16331401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invisible Terror |
E396560
|
entity |
| Predicate | featuresTechnologyType |
P1482
|
FINISHED |
| Object | futuristic 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: futuristic weapon | Statement: [Invisible Terror, featuresTechnologyType, futuristic weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTechnologyType Context triple: [Invisible Terror, featuresTechnologyType, futuristic weapon]
-
A.
technologyType
chosen
Indicates the specific kind or category of technology associated with an entity or relationship.
-
B.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
-
C.
technologyClass
Indicates the classification or category of technology to which an entity belongs.
-
D.
technologyName
Indicates the specific name or designation of a technology associated with an entity.
-
E.
technologyFunction
Indicates the role, purpose, or capability that a technology provides or performs.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4dfd9688190a749e48ebc055baf |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.