Triple

T22554857
Position Surface form Disambiguated ID Type / Status
Subject Six Days’ Campaign E557653 entity
Predicate hasApproximateAlliedStrength P690 FINISHED
Object about 70,000–120,000 troops 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: about 70,000–120,000 troops | Statement: [Six Days’ Campaign, hasApproximateAlliedStrength, about 70,000–120,000 troops]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateAlliedStrength
Context triple: [Six Days’ Campaign, hasApproximateAlliedStrength, about 70,000–120,000 troops]
  • A. hasApproximateDefendingForceSize
    Indicates that an entity is associated with a defending force whose size is known only approximately rather than as an exact value.
  • B. troopStrengthAlliedApprox chosen
    Indicates that the approximate troop strength of one entity is being assessed or reported in relation to its allied forces.
  • C. hasAlliedLeader
    Indicates that one entity serves as an allied leader or commander in relation to another entity.
  • D. alliesIncluded
    Indicates that the specified set or group explicitly includes one or more allied entities as members.
  • E. forceTypeAllied
    Indicates that the force involved is of an allied type relative to a specified reference side or faction.
  • 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_69e11e59db848190b4272ecd2b690ffd completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15f78d8288190871d54db0a7f454b completed April 29, 2026, 1:31 a.m.
PD Predicate disambiguation batch_69e898cb3fb48190add6ab24a2df5822 completed April 22, 2026, 9:45 a.m.
Created at: April 16, 2026, 8:52 p.m.