Triple
T6353498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Fraustadt |
E142933
|
entity |
| Predicate | capturedStandardsBySwedes |
P70144
|
FINISHED |
| Object | over 50 standards and colours |
—
|
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: over 50 standards and colours | Statement: [Battle of Fraustadt, capturedStandardsBySwedes, over 50 standards and colours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedStandardsBySwedes Context triple: [Battle of Fraustadt, capturedStandardsBySwedes, over 50 standards and colours]
-
A.
capturedStandardsByPrussia
Indicates that military standards or flags were seized or taken as trophies by Prussia from another party.
-
B.
strengthSweden
Indicates the level or degree of strength associated with Sweden in a given context.
-
C.
SwedishCasualties
Indicates the number or extent of casualties suffered by Swedish forces or individuals in a given event or context.
-
D.
wasUnderSwedishRuleFrom
Indicates that one entity was governed or controlled by Sweden during a specified time period.
-
E.
coreStandard
Indicates that something conforms to, is defined by, or is governed by a central or foundational standard or specification.
- 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_69c008d6dcbc8190aa1c2f1fd8916b42 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067dec4a88190992d57a0cc7782ad |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:31 p.m.