Triple
T26359544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitwa pod Kockiem |
E660161
|
entity |
| Predicate | unitGermany |
P25051
|
FINISHED |
| Object | 29 Dywizja Zmotoryzowana |
—
|
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: 29 Dywizja Zmotoryzowana | Statement: [Bitwa pod Kockiem, unitGermany, 29 Dywizja Zmotoryzowana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitGermany Context triple: [Bitwa pod Kockiem, unitGermany, 29 Dywizja Zmotoryzowana]
-
A.
objectiveGermany
Indicates that an entity has Germany as its objective, target, or goal in a given context.
-
B.
GermanyFormation
Indicates the event or process by which Germany was established or formed as a political entity.
-
C.
federalStateOfGermany
Indicates that one entity is a federal state (Bundesland) that is a constituent state within the country of Germany.
-
D.
confederationOfGermany
Indicates a relationship in which an entity is part of, associated with, or constitutes the Confederation of Germany as a political union or alliance.
-
E.
germanUnit
chosen
Indicates that an entity is a military or organizational unit that belongs to, originates from, or is associated with Germany.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ff21bc08190994f406feb484aad |
completed | May 2, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 10:50 p.m.