Triple
T1421101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tlaloc |
E30225
|
entity |
| Predicate | receivesSoulsOf |
P26671
|
FINISHED |
| Object | those who die by drowning |
—
|
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: those who die by drowning | Statement: [Tlaloc, receivesSoulsOf, those who die by drowning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesSoulsOf Context triple: [Tlaloc, receivesSoulsOf, those who die by drowning]
-
A.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
B.
judgeOfSoulsWith
Indicates a relationship where one entity evaluates or passes judgment on the souls of other entities, often determining their fate or moral standing.
-
C.
receivesRevelationFrom
Indicates that one entity is the recipient of a revelation, message, or disclosed knowledge that originates from another entity.
-
D.
summoned
Indicates that one entity has called forth, invoked, or ordered the appearance of another entity, typically through authority, command, or supernatural means.
-
E.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
- F. None of above. chosen
Provenance (4 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c42210948190a8fb5e3f9ee3213b |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf0d64c08190ac12977b86fbe4ab |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf8158ac8190b8360ecccc2980bc |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 8 p.m.