Triple
T26786716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo Dooley |
E670398
|
entity |
| Predicate | hasBionicEnhancement |
P41225
|
FINISHED |
| Object | bionic arm (later in series) |
—
|
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: bionic arm (later in series) | Statement: [Leo Dooley, hasBionicEnhancement, bionic arm (later in series)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBionicEnhancement Context triple: [Leo Dooley, hasBionicEnhancement, bionic arm (later in series)]
-
A.
hasCybernetic
chosen
Indicates that an entity possesses or is equipped with cybernetic enhancements, implants, or components.
-
B.
hasExoskeleton
Indicates that an entity possesses an external supportive or protective skeletal structure covering its body.
-
C.
hasBoostMechanic
Indicates that one entity (typically a game or system) includes a mechanic that temporarily increases the power, speed, or effectiveness of another entity.
-
D.
featuresCyborg
Indicates that something includes or prominently presents a cyborg as part of its content or composition.
-
E.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 4:13 a.m.