Triple
T27978342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Szare Szeregi |
E706548
|
entity |
| Predicate | roleInWarsawUprising |
P88009
|
FINISHED |
| Object | combat units |
—
|
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: combat units | Statement: [Szare Szeregi, roleInWarsawUprising, combat units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInWarsawUprising Context triple: [Szare Szeregi, roleInWarsawUprising, combat units]
-
A.
roleInKatynMassacre
Indicates that an entity played a part or held responsibility in the planning, execution, or facilitation of the Katyn Massacre.
-
B.
rolaWZimnejWojnie
Indicates a role or involvement that one entity had in the context of the Cold War.
-
C.
roleInWarOrConflict
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
D.
polishForcesRole
Indicates that an entity serves in, is associated with, or has a specific role within the Polish armed forces.
-
E.
roleInRevolt
chosen
Indicates the specific function, position, or level of participation an entity had within a particular revolt or uprising.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 27, 2026, 7:42 p.m.