Triple
T5911070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cetus |
E131458
|
entity |
| Predicate | causeOfAttack |
P694
|
FINISHED |
| Object | offense of Cassiopeia’s boast |
—
|
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: offense of Cassiopeia’s boast | Statement: [Cetus, causeOfAttack, offense of Cassiopeia’s boast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfAttack Context triple: [Cetus, causeOfAttack, offense of Cassiopeia’s boast]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
C.
attackOccurred
Indicates that an act of aggression or violence was carried out by one party against another.
-
D.
objectiveOfAttackers
Indicates the target or goal that attackers aim to reach or affect through their attack.
-
E.
aimOfAttacker
Indicates that a particular goal, target, or objective is what the attacker intends to achieve or affect.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.