Triple
T31217940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsar Dadon |
E795922
|
entity |
| Predicate | goesToWarBecauseOf |
P93246
|
FINISHED |
| Object | the golden cockerel’s warning |
—
|
NE NERFINISHED |
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: the golden cockerel’s warning | Statement: [Tsar Dadon, goesToWarBecauseOf, the golden cockerel’s warning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goesToWarBecauseOf Context triple: [Tsar Dadon, goesToWarBecauseOf, the golden cockerel’s warning]
-
A.
goalDuringWar
Indicates that a particular goal or objective is pursued, exists, or is relevant during the time period of a war or armed conflict.
-
B.
reasonForAttack
chosen
Indicates that one entity’s attack on another is motivated or caused by the specified reason.
-
C.
blamesForWar
Indicates that one entity holds another entity responsible for causing or contributing to a war.
-
D.
almostLedToWarIn
Indicates that one entity’s actions or circumstances brought it very close to causing a war in a specified place or context, but the war ultimately did not occur.
-
E.
reasonForEnlistment
Indicates the motivation, cause, or circumstances that led an individual to join a military or similar organized service.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c49a8888190ab9e0382cbc7be98 |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.