Triple
T17717838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian corps under Korsakov |
E442251
|
entity |
| Predicate | resultAtSecondBattleOfZurich |
P128711
|
FINISHED |
| Object | defeat |
—
|
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: defeat | Statement: [Russian corps under Korsakov, resultAtSecondBattleOfZurich, defeat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultAtSecondBattleOfZurich Context triple: [Russian corps under Korsakov, resultAtSecondBattleOfZurich, defeat]
-
A.
resultOfSecondAttack
Indicates that an event or state occurs as a consequence of a second attack in a sequence of attacks.
-
B.
operationInSecondBattle
Indicates that an entity participated in or was involved in a military operation that took place during the second battle of a given conflict.
-
C.
secondFight
Indicates that an entity engages in a second instance of a fight or combat interaction with another entity.
-
D.
secondFightCity
Indicates that an entity engaged in its second fight or battle in the specified city.
-
E.
resultOfSiege
Indicates that one entity is the outcome or consequence produced by a siege conducted against another entity.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e474834aec81909ab7e8224c5a39d7 |
completed | April 19, 2026, 6:21 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d018227c8190b6624a2199e765e8 |
completed | April 18, 2026, 6:40 p.m. |
Created at: April 10, 2026, 10:06 a.m.