Triple
T32276468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cerro Corá |
E824559
|
entity |
| Predicate | commanderParaguay |
P189355
|
FINISHED |
| Object | Francisco Solano López |
—
|
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: Francisco Solano López | Statement: [Battle of Cerro Corá, commanderParaguay, Francisco Solano López]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderParaguay Context triple: [Battle of Cerro Corá, commanderParaguay, Francisco Solano López]
-
A.
commanderArgentina
Indicates that one entity serves as the military or organizational commander of Argentina.
-
B.
commanderForChile
Indicates that an individual serves or has served as a military or organizational commander on behalf of Chile.
-
C.
commanderForPeru
Indicates that an entity serves or has served as a military commander on behalf of Peru.
-
D.
commanderForBrazil
Indicates that an entity serves or has served as a military commander for Brazil.
-
E.
commanderForGovernment
Indicates that an entity serves as a military or organizational commander on behalf of, or within the authority structure of, a specific government.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 1, 2026, 12:43 a.m.