Triple
T3285730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Right Hand of Doom |
E68976
|
entity |
| Predicate | sideOfBody |
P37323
|
FINISHED |
| Object | right 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: right hand | Statement: [Right Hand of Doom, sideOfBody, right hand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideOfBody Context triple: [Right Hand of Doom, sideOfBody, right hand]
-
A.
bodySideOrientation
chosen
Indicates the spatial relationship of an entity with respect to the left, right, or bilateral side of a body.
-
B.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
C.
hasBodyRegion
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
D.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
E.
situatedOnSideOf
Indicates that one entity is located along or beside the lateral part or edge of another entity.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb03918c48190987d7cfd3bda9716 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.