Triple
T940818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Baltic Front |
E20300
|
entity |
| Predicate | frontCommanderRank |
P2084
|
FINISHED |
| Object | Army 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: Army General | Statement: [1st Baltic Front, frontCommanderRank, Army General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontCommanderRank Context triple: [1st Baltic Front, frontCommanderRank, Army General]
-
A.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
B.
commanderTitle
chosen
Indicates the official rank or title held by the person who commands or leads a given entity.
-
C.
chiefOfStaff
Indicates that one entity serves as the chief of staff for another entity, typically managing operations and coordinating activities on its behalf.
-
D.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
E.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b38cc6888190b1d9043ec8fbcbc3 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.