Triple
T4648990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shades in the Underworld |
E102242
|
entity |
| Predicate | transitionedBy |
P26626
|
FINISHED |
| Object | Death of the body |
—
|
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: Death of the body | Statement: [Shades in the Underworld, transitionedBy, Death of the body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionedBy Context triple: [Shades in the Underworld, transitionedBy, Death of the body]
-
A.
transitionTo
Indicates a change in state, condition, or phase from one defined status to another.
-
B.
transitionedInto
Indicates that one entity changed state, form, role, or condition to become another specified state or entity.
-
C.
transition
chosen
Indicates a change of state or condition from one form, phase, or situation to another.
-
D.
transiting
Indicates that an entity is in the process of passing through, across, or between locations or states, typically as part of a journey or transfer.
-
E.
transitionProgram
Indicates a relationship where one entity serves as a program or structured process that facilitates another entity’s transition from one state, phase, or condition to another.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.