Triple

T2078238
Position Surface form Disambiguated ID Type / Status
Subject Warsaw Pact invasion of Czechoslovakia E44977 entity
Predicate tankStrengthInvadingForces P5289 FINISHED
Object approximately 2000 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: approximately 2000 | Statement: [Warsaw Pact invasion of Czechoslovakia, tankStrengthInvadingForces, approximately 2000]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tankStrengthInvadingForces
Context triple: [Warsaw Pact invasion of Czechoslovakia, tankStrengthInvadingForces, approximately 2000]
  • A. combatantStrength
    Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
  • B. besiegingForce
    Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
  • C. primaryEnemyForces
    Indicates that the related entities constitute the main opposing or hostile forces in a conflict or competitive situation.
  • D. numberOfTanks chosen
    Indicates the quantity or count of tanks associated with a given entity or context.
  • E. warTimeStrengthApprox
    Indicates an approximate measure of an entity’s military strength or capacity during a time of war.
  • 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_69a88916c2b48190a5ca2e9b12cad3ed completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abba31eef8819081cf7f5334b59fe1 completed March 7, 2026, 5:40 a.m.
PD Predicate disambiguation batch_69abb7b0edac8190a58eabee55f73deb completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:41 p.m.