Triple
T7370285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kock |
E169981
|
entity |
| Predicate | GermanCommanderRank |
P30999
|
FINISHED |
| Object | General |
—
|
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: General | Statement: [Battle of Kock, GermanCommanderRank, General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GermanCommanderRank Context triple: [Battle of Kock, GermanCommanderRank, General]
-
A.
germanCommander
Indicates that the subject serves as a military commander for German forces in relation to the object.
-
B.
PrussianCommander
Indicates that an individual holds the position or role of a commander within the Prussian military forces.
-
C.
hasCommanderRank
chosen
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
D.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
E.
commanderInChiefRank
Indicates that an entity holds the highest-ranking leadership position over a military or armed forces organization.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f182df5c81908964fbaa3f8ec790 |
completed | March 27, 2026, 9:07 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:07 p.m.