Triple
T18694701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | death of Achilles |
E457087
|
entity |
| Predicate | involvesBodyPart |
P21283
|
FINISHED |
| Object | heel of Achilles |
—
|
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: heel of Achilles | Statement: [death of Achilles, involvesBodyPart, heel of Achilles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesBodyPart Context triple: [death of Achilles, involvesBodyPart, heel of Achilles]
-
A.
typicalBodyPart
Indicates that one entity is a body part that is characteristically or normally associated with another entity.
-
B.
injuredBodyPart
Indicates that an entity has sustained an injury specifically affecting a particular body part.
-
C.
hasBodyRegion
chosen
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
D.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
E.
isProminentPartOf
Indicates that something forms a major, highly noticeable, or significant component of a larger whole.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e66a188190801fd95f9be26042 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.