Triple
T30974979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provincia de Arturo Prat |
E789205
|
entity |
| Predicate | namedForBattle |
P23441
|
FINISHED |
| Object | Battle of Iquique |
—
|
NE NERFINISHED |
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: Battle of Iquique | Statement: [Provincia de Arturo Prat, namedForBattle, Battle of Iquique]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForBattle Context triple: [Provincia de Arturo Prat, namedForBattle, Battle of Iquique]
-
A.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
B.
usedInBattle
Indicates that something (typically a tool, strategy, or resource) was employed or applied during a battle or combat situation.
-
C.
associatedWithBattle
chosen
Indicates a relationship where an entity is connected or linked to a specific battle, such as by participation, relevance, or involvement.
-
D.
flagshipDuringBattle
Indicates that one entity serves as the primary command ship for another entity during a specific battle or military engagement.
-
E.
allyInBattle
Indicates that two or more entities cooperate on the same side as partners during a specific battle or combat situation.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 8:55 p.m.