Triple
T18151906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schlacht bei Kay |
E434523
|
entity |
| Predicate | WaffengattungPreußen |
P16410
|
FINISHED |
| Object | Infanterie |
—
|
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: Infanterie | Statement: [Schlacht bei Kay, WaffengattungPreußen, Infanterie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WaffengattungPreußen Context triple: [Schlacht bei Kay, WaffengattungPreußen, Infanterie]
-
A.
militaryBranchPrussia
Indicates that an entity served as a branch or component of the military forces of Prussia.
-
B.
PrussianStrength
Indicates a relationship where an entity possesses or exhibits the military, political, or institutional power characteristic of Prussia.
-
C.
PrussianStrengthApprox
Indicates an approximate assessment or estimation of the strength or power associated with Prussia in a given context.
-
D.
weaponCategory
chosen
Indicates the classification or type of weapon to which an item or armament belongs.
-
E.
gunType
Indicates the specific category or kind of gun associated with an entity.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de38d4e08190bc4d430b70b7e288 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.