Triple
T8752246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilean corvette Esmeralda |
E207986
|
entity |
| Predicate | sinkingPlace |
P10135
|
FINISHED |
| Object | off Iquique, Peru |
—
|
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: off Iquique, Peru | Statement: [Chilean corvette Esmeralda, sinkingPlace, off Iquique, Peru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sinkingPlace Context triple: [Chilean corvette Esmeralda, sinkingPlace, off Iquique, Peru]
-
A.
sunkPlace
chosen
Indicates that one entity caused another (typically a vessel or structure) to sink at a specific location.
-
B.
subterranean
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
-
C.
sinkingConsequence
Indicates the outcome or effect that results from something sinking.
-
D.
sunk
Indicates that one entity caused another entity to go below the surface of a liquid, typically water, so that it is submerged or destroyed.
-
E.
buriedUnder
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5da8cc548190a31ad542d2faf2d5 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.