Triple
T8752300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Iquique |
E207987
|
entity |
| Predicate | primaryEngagementBetween |
P80144
|
FINISHED |
| Object | Esmeralda and Huáscar |
—
|
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: Esmeralda and Huáscar | Statement: [Battle of Iquique, primaryEngagementBetween, Esmeralda and Huáscar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEngagementBetween Context triple: [Battle of Iquique, primaryEngagementBetween, Esmeralda and Huáscar]
-
A.
primaryEngagement
Indicates the main or most significant interaction, involvement, or relationship that an entity has with another entity or activity.
-
B.
primaryInteraction
chosen
Indicates the main or most significant interaction occurring between the involved entities.
-
C.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
D.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
E.
seeksEngagementWith
Indicates an entity’s active effort or intention to initiate or maintain interaction, involvement, or responsive connection with another entity.
- 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.