Triple
T21884119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Cocalus |
E540361
|
entity |
| Predicate | deathOfMinosMethod |
P48923
|
FINISHED |
| Object | scalding in a bath |
—
|
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: scalding in a bath | Statement: [King Cocalus, deathOfMinosMethod, scalding in a bath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathOfMinosMethod Context triple: [King Cocalus, deathOfMinosMethod, scalding in a bath]
-
A.
dedicatedToAspectOfAnubis
Indicates that something (such as a temple, object, or practice) is devoted or consecrated specifically to a particular aspect or manifestation of the deity Anubis.
-
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.
hasMannerOfDeath
chosen
Indicates the specific way or circumstances in which an entity died, such as natural causes, accident, homicide, or suicide.
-
D.
methodOfSacrifice
Indicates the specific way or procedure by which a sacrifice is carried out.
-
E.
positionAmongMoirai
Indicates the specific rank or placement an entity holds within the group of the Moirai (the Fates) relative to the others.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118e9d3508190aadcfcdac0376387 |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.