Triple
T29228618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luphomoid (MCU) |
E741001
|
entity |
| Predicate | cyberneticsUsage |
P41225
|
FINISHED |
| Object | common among Thanos-aligned Luphomoids (implied from Nebula) |
—
|
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: common among Thanos-aligned Luphomoids (implied from Nebula) | Statement: [Luphomoid (MCU), cyberneticsUsage, common among Thanos-aligned Luphomoids (implied from Nebula)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cyberneticsUsage Context triple: [Luphomoid (MCU), cyberneticsUsage, common among Thanos-aligned Luphomoids (implied from Nebula)]
-
A.
hasCybernetic
chosen
Indicates that an entity possesses or is equipped with cybernetic enhancements, implants, or components.
-
B.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
C.
technologyUsedFor
Indicates that a particular technology is employed or applied to accomplish, support, or enable a specific purpose, task, or function.
-
D.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
E.
usedCommandAndControlSystem
Indicates that an entity employed a specific command-and-control system to coordinate, manage, or direct operations or activities.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:17 p.m.