Triple
T27419467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotwang |
E692998
|
entity |
| Predicate | hasArtificialLimb |
P54723
|
FINISHED |
| Object | mechanical hand |
—
|
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: mechanical hand | Statement: [Rotwang, hasArtificialLimb, mechanical hand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtificialLimb Context triple: [Rotwang, hasArtificialLimb, mechanical hand]
-
A.
hasProsthesis
chosen
Indicates that an entity possesses or is equipped with an artificial substitute for a missing or impaired body part.
-
B.
hasLimb
Indicates that an entity possesses a specific limb as part of its body.
-
C.
lostLimb
Indicates that an entity has had one or more of its limbs removed or rendered permanently absent, typically as a result of injury, surgery, or trauma.
-
D.
hasMechanicalAppendages
Indicates that an entity possesses one or more appendages that are mechanical or artificially constructed rather than purely biological.
-
E.
hasExoskeleton
Indicates that an entity possesses an external supportive or protective skeletal structure covering its body.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 12:35 p.m.