Triple
T37165064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TsShPD |
E920770
|
entity |
| Predicate | coordinatedForces |
P61211
|
FINISHED |
| Object | Soviet partisans |
—
|
NE NERFINISHED |
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: Soviet partisans | Statement: [TsShPD, coordinatedForces, Soviet partisans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinatedForces Context triple: [TsShPD, coordinatedForces, Soviet partisans]
-
A.
commandedForcesOf
Indicates that one entity held command authority over the military or armed forces associated with another entity.
-
B.
commandedForcesAgainst
Indicates that one entity held command authority over military or armed forces engaged in opposition to another entity.
-
C.
commandedForcesFrom
Indicates that one entity held command authority over military or organizational forces originating from another entity.
-
D.
alliedForces
chosen
Indicates that multiple entities are cooperating militarily or strategically as part of the same alliance or coalition.
-
E.
UnionForcesType
Indicates that one entity is associated with, composed of, or characterized by a specific type or category of union forces.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:15 p.m.