Triple
T33360772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of New Ulm |
E854213
|
entity |
| Predicate | partiallyEvacuated |
P185678
|
FINISHED |
| Object | New Ulm |
—
|
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: New Ulm | Statement: [Battle of New Ulm, partiallyEvacuated, New Ulm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyEvacuated Context triple: [Battle of New Ulm, partiallyEvacuated, New Ulm]
-
A.
partiallyDestroyed
Indicates that an entity has been damaged or ruined to a significant extent but not completely destroyed.
-
B.
partiallyRelocated
Indicates that an entity has been moved from its original location to a new one, but the relocation is incomplete or only affects part of the entity or its components.
-
C.
partlyCollapsedInto
Indicates that one entity has partially fallen or sunk into another entity, resulting in an incomplete or partial collapse into it.
-
D.
partiallyRestored
Indicates that an entity has been brought back toward a previous or original state, but the restoration is incomplete or only partially achieved.
-
E.
partiallyReleased
Indicates that an entity has been released to some extent but not yet fully or completely released.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 1, 2026, 1:34 a.m.