Triple
T28933512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Death plague |
E733850
|
entity |
| Predicate | embodiedAs |
P142328
|
FINISHED |
| Object | tall and gaunt figure |
—
|
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: tall and gaunt figure | Statement: [Red Death plague, embodiedAs, tall and gaunt figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: embodiedAs Context triple: [Red Death plague, embodiedAs, tall and gaunt figure]
-
A.
embodiedBy
Indicates that an abstract concept, role, or function is physically or concretely realized in a specific entity.
-
B.
embodimentCondition
Indicates the condition or circumstances under which an abstract entity or concept is realized, instantiated, or given concrete form in a particular embodiment.
-
C.
representedBody
Indicates that one entity serves as a symbolic, artistic, or conceptual depiction of another entity’s body or physical form.
-
D.
embodiesValue
Indicates that an entity exemplifies, represents, or gives concrete form to a particular value, principle, or ideal.
-
E.
isConceptualizedAs
chosen
Indicates that one entity is mentally represented, interpreted, or understood in terms 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b5453d0819082d3783b3b11019a |
completed | May 2, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:30 a.m.