Triple
T25420493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsyas |
E636967
|
entity |
| Predicate | transformationAfterDeath |
P85351
|
FINISHED |
| Object | associated with a river bearing his name |
—
|
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: associated with a river bearing his name | Statement: [Marsyas, transformationAfterDeath, associated with a river bearing his name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transformationAfterDeath Context triple: [Marsyas, transformationAfterDeath, associated with a river bearing his name]
-
A.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
B.
movementAfterDeath
Indicates a movement or relocation that occurs after an entity has died or ceased living.
-
C.
afterDeathOf
Indicates that one event, state, or condition occurs subsequent to and as a result of the death of a specified entity.
-
D.
wasTransformedBy
chosen
Indicates that an entity has undergone a change of state, form, or condition as the result of an action, process, or agent.
-
E.
afterlife
Indicates a relationship where an entity exists or experiences a state following physical death or the end of mortal life.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 1:56 p.m.