Triple
T1556804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sisyphus |
E33222
|
entity |
| Predicate | revealedSecretOf |
P30306
|
FINISHED |
| Object | Zeus’s abduction of Aegina |
—
|
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: Zeus’s abduction of Aegina | Statement: [Sisyphus, revealedSecretOf, Zeus’s abduction of Aegina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revealedSecretOf Context triple: [Sisyphus, revealedSecretOf, Zeus’s abduction of Aegina]
-
A.
revealedAfter
Indicates that one piece of information, event, or state becomes known or disclosed only subsequent to another specified point in time or condition.
-
B.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
C.
hasModeOfRevelation
Indicates the manner or channel through which something is revealed, communicated, or made known.
-
D.
secretive
Indicates that an entity deliberately withholds information or conceals its thoughts, actions, or intentions from others.
-
E.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9407d9d1481909597af97b16512cc |
completed | March 5, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69a907b688d081908171f89010c53973 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a9407aa20881909e747f247ccec642 |
completed | March 5, 2026, 8:36 a.m. |
Created at: March 4, 2026, 7:27 p.m.