Triple
T34267275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Cepheus (Clash of the Titans) |
E879204
|
entity |
| Predicate | indirectlyProvokes |
P54036
|
FINISHED |
| Object | divine punishment against Argos |
—
|
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: divine punishment against Argos | Statement: [King Cepheus (Clash of the Titans), indirectlyProvokes, divine punishment against Argos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indirectlyProvokes Context triple: [King Cepheus (Clash of the Titans), indirectlyProvokes, divine punishment against Argos]
-
A.
instigates
Indicates that one entity initiates, provokes, or sets in motion an action, event, or response in another.
-
B.
provokesEmotionType
Indicates that one entity causes or elicits a specific type of emotional response in another entity.
-
C.
indirectImpactOn
chosen
Indicates that one entity affects another entity’s state, condition, or outcome through one or more intermediate factors rather than through a direct interaction.
-
D.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
E.
indirectlyDefeated
Indicates that one entity caused or contributed to another entity’s defeat through intermediate actions, agents, or events rather than by defeating it directly.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.