Triple
T10512513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Chopper |
E247949
|
entity |
| Predicate | bodyPartReplacedWithMetal |
P59925
|
FINISHED |
| Object | arms |
—
|
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: arms | Statement: [Nick Chopper, bodyPartReplacedWithMetal, arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyPartReplacedWithMetal Context triple: [Nick Chopper, bodyPartReplacedWithMetal, arms]
-
A.
hasReconstructionMaterial
chosen
Indicates that something is associated with, composed of, or utilizes a particular material for its reconstruction.
-
B.
replacedChamber
Indicates that one chamber has been substituted for or has taken the place of another chamber.
-
C.
allMetalConstruction
Indicates that something is constructed entirely or almost entirely from metal components.
-
D.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
E.
replacedInProduct
Indicates that one component or element in a product has been substituted or superseded by another component or element within that product.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509ca214481909b3ed9265e7a6704 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:27 p.m.