Triple
T35208156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dis-arm-her |
E1016596
|
entity |
| Predicate | targetsBodyPart |
P198091
|
FINISHED |
| Object | arm |
—
|
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: arm | Statement: [Dis-arm-her, targetsBodyPart, arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsBodyPart Context triple: [Dis-arm-her, targetsBodyPart, arm]
-
A.
targetsBody
Indicates that one entity is directed at, aimed at, or focused on affecting the body of another entity.
-
B.
typicalBodyPart
Indicates that one entity is a body part that is characteristically or normally associated with another entity.
-
C.
balancingBodyParts
Indicates that an entity is using specific body parts to maintain or control physical balance.
-
D.
legendaryBodyPart
Indicates that a body part is of legendary status, typically renowned in myth, folklore, or extraordinary tales for its exceptional qualities or significance.
-
E.
partOfBodyWith
Indicates that one entity is a body part that belongs to, or is physically contained within, another entity.
- F. None of above. chosen
Provenance (4 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69fec8adaa308190a9a276f8c36f15f0 |
completed | May 9, 2026, 5:39 a.m. |
Created at: May 3, 2026, 4:02 p.m.