Triple
T36964228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark of the Outsider |
E914384
|
entity |
| Predicate | typicalLocationOnBody |
P32348
|
FINISHED |
| Object | back of the 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: back of the hand | Statement: [Mark of the Outsider, typicalLocationOnBody, back of the hand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationOnBody Context triple: [Mark of the Outsider, typicalLocationOnBody, back of the hand]
-
A.
locatedOnBody
chosen
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
B.
discoveredOnBody
Indicates that something (such as an item, mark, or substance) was found on the surface or person of a body.
-
C.
typicalOnsetLocation
Indicates the anatomical location where a condition, symptom, or process most commonly begins or first appears.
-
D.
typicalBodyPart
Indicates that one entity is a body part that is characteristically or normally associated with another entity.
-
E.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.