Triple
T30014429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Reserve Army |
E762555
|
entity |
| Predicate | participatingForceIn |
P39448
|
FINISHED |
| Object | Soviet–German War |
—
|
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–German War | Statement: [3rd Reserve Army, participatingForceIn, Soviet–German War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatingForceIn Context triple: [3rd Reserve Army, participatingForceIn, Soviet–German War]
-
A.
forzaBelligerante
Indicates a party’s status or role as a belligerent force engaged in a conflict or war.
-
B.
armedForcesInvolved
chosen
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
C.
involvedForcesType
Indicates the type or category of forces that participate in or are associated with a given event, interaction, or situation.
-
D.
isPrimaryLandForceOf
Indicates that a military land force serves as the main or principal ground combat component of a specified country, alliance, or organization.
-
E.
stateOfForces
Indicates the condition, disposition, or readiness level of military or organizational forces at a given time.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 29, 2026, 6:45 p.m.