Triple
T5217252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Clouds |
E117782
|
entity |
| Predicate | causeOfAbort |
P694
|
FINISHED |
| Object | severe rainstorm |
—
|
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: severe rainstorm | Statement: [Battle of the Clouds, causeOfAbort, severe rainstorm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfAbort Context triple: [Battle of the Clouds, causeOfAbort, severe rainstorm]
-
A.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
B.
reasonForAnnulment
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
-
C.
reasonForException
Indicates the specific cause or justification for why a normal rule, process, or condition does not apply in a given case.
-
D.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
E.
retreatCause
Indicates that one event, condition, or factor serves as the reason or trigger for a retreat by an entity.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a95abdc8190b0babd79cea1360e |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.