Triple
T38368539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amban phase-pulse blaster |
E892516
|
entity |
| Predicate | universeTechnologyType |
P1482
|
FINISHED |
| Object | blaster 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: blaster technology | Statement: [Amban phase-pulse blaster, universeTechnologyType, blaster technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universeTechnologyType Context triple: [Amban phase-pulse blaster, universeTechnologyType, blaster technology]
-
A.
inUniverseTechnologyOf
Indicates that a technology exists within, and is part of, the fictional universe or setting associated with a given entity.
-
B.
inUniverseTechnologyDeveloped
Indicates that a specific technology has been created or developed within the context of a particular fictional or defined universe.
-
C.
technologyType
chosen
Indicates the specific kind or category of technology associated with an entity or relationship.
-
D.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
E.
spaceConcept
Indicates a conceptual or abstract relationship involving space, such as spatial properties, structures, or organizational principles, rather than specific physical locations or objects.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.