Triple
T2259231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ever Given |
E49997
|
entity |
| Predicate | groundingCause |
P694
|
FINISHED |
| Object | loss of steering in high winds and poor visibility |
—
|
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: loss of steering in high winds and poor visibility | Statement: [Ever Given, groundingCause, loss of steering in high winds and poor visibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundingCause Context triple: [Ever Given, groundingCause, loss of steering in high winds and poor visibility]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
C.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
D.
causeSupported
Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
-
E.
groundComponent
Indicates that one entity serves as a foundational or base part upon which another entity is built, attached, or functionally dependent.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc15ad06c8190b6d0babc17015787 |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:48 p.m.