Triple

T30373138
Position Surface form Disambiguated ID Type / Status
Subject Tarakan operation E772604 entity
Predicate forceStrengthAllied P690 FINISHED
Object approximately 12,000 personnel 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 12,000 personnel | Statement: [Tarakan operation, forceStrengthAllied, approximately 12,000 personnel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: forceStrengthAllied
Context triple: [Tarakan operation, forceStrengthAllied, approximately 12,000 personnel]
  • A. forceTypeAllied
    Indicates that the force involved is of an allied type relative to a specified reference side or faction.
  • B. commandingForce2Strength
    Indicates that a commanding force possesses or exerts a particular level or measure of strength.
  • C. troopStrengthAlliedApprox chosen
    Indicates that the approximate troop strength of one entity is being assessed or reported in relation to its allied forces.
  • D. alliedForces
    Indicates that multiple entities are cooperating militarily or strategically as part of the same alliance or coalition.
  • E. commandingForce1Strength
    Indicates that one entity has a certain level or measure of strength in its role as the primary commanding force over another entity or situation.
  • 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_69f2248d71408190aec0d5c2001b1cff completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6828532d081909897bbe49b280ced completed May 2, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69f678d019fc8190913662cd2f87b857 completed May 2, 2026, 10:21 p.m.
Created at: April 29, 2026, 7:59 p.m.