Triple

T38085949
Position Surface form Disambiguated ID Type / Status
Subject Okehazama no Tatakai E950976 entity
Predicate approximateStrengthOda P2981 FINISHED
Object around 2,000–3,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: around 2,000–3,000 troops | Statement: [Okehazama no Tatakai, approximateStrengthOda, around 2,000–3,000 troops]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: approximateStrengthOda
Context triple: [Okehazama no Tatakai, approximateStrengthOda, around 2,000–3,000 troops]
  • A. estimatedStrength chosen
    Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
  • B. availableStrength
    Indicates the amount of strength or power that an entity currently has ready for use or deployment.
  • C. approximateRoyalStrength
    Indicates an estimated or inferred level of royal power, influence, or capability rather than a precisely measured one.
  • D. initialStrength
    Indicates the original or starting level of strength associated with an entity before any changes or influences occur.
  • E. hasTypicalStrength
    Indicates that an entity possesses the usual or characteristic level of strength expected for its kind or context.
  • 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_69f76f03a3608190a73fd6df87c792a8 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fff09dae088190bd8460060d778feb completed May 10, 2026, 2:42 a.m.
PD Predicate disambiguation batch_69fff0027c5c8190baa5c7a15852cbe0 completed May 10, 2026, 2:40 a.m.
Created at: May 3, 2026, 4:21 p.m.