Triple
T13699914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Mnemonic (character) |
E328488
|
entity |
| Predicate | hasCyberneticImplant |
P41225
|
FINISHED |
| Object | brain data storage implant |
—
|
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: brain data storage implant | Statement: [Johnny Mnemonic (character), hasCyberneticImplant, brain data storage implant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCyberneticImplant Context triple: [Johnny Mnemonic (character), hasCyberneticImplant, brain data storage implant]
-
A.
hasCybernetic
chosen
Indicates that an entity possesses or is equipped with cybernetic enhancements, implants, or components.
-
B.
hasProsthesis
Indicates that an entity possesses or is equipped with an artificial substitute for a missing or impaired body part.
-
C.
hasExoskeleton
Indicates that an entity possesses an external supportive or protective skeletal structure covering its body.
-
D.
hasGadget
Indicates that an entity possesses, uses, or is equipped with a particular gadget.
-
E.
featuresCyborg
Indicates that something includes or prominently presents a cyborg as part of its content or composition.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc879adc88190b03f1cf815b71061 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.