Triple
T31324365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French frigate Méduse |
E798840
|
entity |
| Predicate | shipwreckCause |
P27489
|
FINISHED |
| Object | grounding on sandbank |
—
|
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: grounding on sandbank | Statement: [French frigate Méduse, shipwreckCause, grounding on sandbank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipwreckCause Context triple: [French frigate Méduse, shipwreckCause, grounding on sandbank]
-
A.
causeOfShipwreck
chosen
Indicates the factor, event, or condition that directly led to a shipwreck occurring.
-
B.
shipwreckEvent
Indicates an event in which a ship is destroyed, stranded, or severely damaged, typically resulting in loss or abandonment at sea or near a shoreline.
-
C.
shipwreck
Indicates that a vessel has been destroyed, stranded, or severely damaged, typically at sea or near a shoreline.
-
D.
shipwreckType
Indicates the specific kind or classification of a shipwreck associated with an entity.
-
E.
shipwreckUse
Indicates that an entity makes use of, interacts with, or derives benefit from a shipwreck.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69eb008808190bdf42de72d202baf |
completed | May 3, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:15 p.m.