Triple
T18510796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Santa Cruz de Tenerife (1657) |
E452336
|
entity |
| Predicate | EnglishTreasureCaptured |
P131956
|
FINISHED |
| Object | minimal |
—
|
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: minimal | Statement: [Battle of Santa Cruz de Tenerife (1657), EnglishTreasureCaptured, minimal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EnglishTreasureCaptured Context triple: [Battle of Santa Cruz de Tenerife (1657), EnglishTreasureCaptured, minimal]
-
A.
plunderedItem
Indicates that an item has been taken or looted by force, typically during a raid, conflict, or act of theft.
-
B.
capturedShip
Indicates that one party has taken control of another party's ship, typically by force or seizure.
-
C.
lootedBy
Indicates that something has been forcibly taken or plundered by a specified agent or group.
-
D.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by another entity.
-
E.
treasureMadeFor
Indicates that a treasure was specifically created, crafted, or designated for a particular recipient, purpose, or context.
- F. None of above. chosen
Provenance (4 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533457e608190988304bf8bc2db1c |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:36 a.m.