Triple
T10188026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-20 |
E236959
|
entity |
| Predicate | reasonForLoss |
P59430
|
FINISHED |
| Object | ran aground in bad weather |
—
|
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: ran aground in bad weather | Statement: [U-20, reasonForLoss, ran aground in bad weather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForLoss Context triple: [U-20, reasonForLoss, ran aground in bad weather]
-
A.
causedLossOf
chosen
Indicates that one entity brought about or was responsible for another entity experiencing a loss.
-
B.
reasonForForfeiture
Indicates the cause or justification that led to something being surrendered, lost, or taken away.
-
C.
reasonForElimination
Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
-
D.
reasonForLossOfVote
Indicates the specific cause or circumstance that led to an entity losing its right or ability to vote.
-
E.
reasonForRelease
Indicates the cause, justification, or circumstance that led to an entity being released.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded7a7aac8190af8dcb8374e62d68 |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.