Triple
T940835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Baltic Front |
E20300
|
entity |
| Predicate | includedBranch |
P6271
|
FINISHED |
| Object | rifle armies |
—
|
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: rifle armies | Statement: [1st Baltic Front, includedBranch, rifle armies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedBranch Context triple: [1st Baltic Front, includedBranch, rifle armies]
-
A.
involvedBranch
chosen
Indicates that a particular branch (such as a location, division, or sub-unit) participates in, is associated with, or plays a role in the referenced event, process, or relationship.
-
B.
branchesFrom
Indicates that one entity originates or diverges from another as a subordinate or offshoot path, structure, or lineage.
-
C.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
D.
usedByBranch
Indicates that something (such as a resource, configuration, or component) is utilized or depended upon by a particular branch.
-
E.
parentBranch
Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
- 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.