Triple
T32203643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Curupayty |
E822611
|
entity |
| Predicate | riverineAspect |
P162290
|
FINISHED |
| Object | operations along the Paraguay River |
—
|
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: operations along the Paraguay River | Statement: [Battle of Curupayty, riverineAspect, operations along the Paraguay River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverineAspect Context triple: [Battle of Curupayty, riverineAspect, operations along the Paraguay River]
-
A.
riverineLocation
Indicates that something is located in, along, or directly associated with a river or river system.
-
B.
riverPhenomenon
Indicates a natural event, condition, or process that occurs in or directly affects a river.
-
C.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
D.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
E.
useRiverSystems
chosen
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 12:36 a.m.