Triple
T4777125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Szare Szeregi |
E106077
|
entity |
| Predicate | GrupySzturmoweRole |
P9463
|
FINISHED |
| Object | older scouts for combat and special operations |
—
|
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: older scouts for combat and special operations | Statement: [Szare Szeregi, GrupySzturmoweRole, older scouts for combat and special operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GrupySzturmoweRole Context triple: [Szare Szeregi, GrupySzturmoweRole, older scouts for combat and special operations]
-
A.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
B.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
roleInMissions
Indicates the specific function, duty, or position an entity holds within one or more missions.
-
D.
ethnicGroupOfCommand
Indicates that a particular ethnic group is associated with, or has control over, a specific command or military/organizational leadership structure.
-
E.
allowedCombatRoles
Indicates the combat roles that an entity is permitted or authorized to perform.
- 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.