Triple
T31977721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ixion |
E816491
|
entity |
| Predicate | statusBeforePunishment |
P197099
|
FINISHED |
| Object | guest of the Olympian gods |
—
|
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: guest of the Olympian gods | Statement: [Ixion, statusBeforePunishment, guest of the Olympian gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusBeforePunishment Context triple: [Ixion, statusBeforePunishment, guest of the Olympian gods]
-
A.
statusBeforeOffensive
Indicates the status or condition of an entity immediately prior to the start of an offensive action or operation.
-
B.
hasPunishment
Indicates that an entity is subject to a specified penalty, sanction, or adverse consequence as a result of some action, condition, or rule.
-
C.
statusBeforeCaptivity
Indicates the condition or state an entity was in immediately prior to entering captivity.
-
D.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
E.
reasonForPunishment
Indicates that one entity is the cause, justification, or grounds for another entity receiving a punishment.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
| PDg | Predicate description generation | batch_69fe779167648190936bd49cc1049178 |
completed | May 8, 2026, 11:53 p.m. |
Created at: May 1, 2026, 12:11 a.m.