Triple
T8752302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Iquique |
E207987
|
entity |
| Predicate | outcomeForEsmeralda |
P59870
|
FINISHED |
| Object | sunk |
—
|
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: sunk | Statement: [Battle of Iquique, outcomeForEsmeralda, sunk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForEsmeralda Context triple: [Battle of Iquique, outcomeForEsmeralda, sunk]
-
A.
timeOfCondemnation
Indicates the specific time at which a condemnation (such as a legal judgment or formal denunciation) occurs or is issued.
-
B.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
C.
perpetratorDeath
Indicates that the referenced individual is the one who caused or is responsible for another entity’s death.
-
D.
outcomeForAccusers
Indicates the result or consequence experienced by the accusers as a result of a particular event, process, or decision.
-
E.
outcomeOfTrial
Indicates that a particular result or verdict is produced as the consequence of a specific trial or legal proceeding.
- 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.