Triple
T4698333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guerra del Asiento |
E104204
|
entity |
| Predicate | batallaImportante |
P21565
|
FINISHED |
| Object | sitio de Cartagena de Indias (1741) |
—
|
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: sitio de Cartagena de Indias (1741) | Statement: [Guerra del Asiento, batallaImportante, sitio de Cartagena de Indias (1741)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batallaImportante Context triple: [Guerra del Asiento, batallaImportante, sitio de Cartagena de Indias (1741)]
-
A.
hasSignificantBattle
chosen
Indicates that a major or decisive battle occurred involving the related entities.
-
B.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
-
C.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
D.
battleDepicted
Indicates that a work or representation visually portrays a specific battle or combat event.
-
E.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.