Triple
T34404402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headquarters and Headquarters Company |
E883068
|
entity |
| Predicate | typicalStrengthRange |
—
|
GENERATED |
| Object | 100–200 soldiers |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStrengthRange Context triple: [Headquarters and Headquarters Company, typicalStrengthRange, 100–200 soldiers]
-
A.
hasTypicalStrength
Indicates that an entity possesses the usual or characteristic level of strength expected for its kind or context.
-
B.
typicalRange
chosen
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
availableStrength
Indicates the amount of strength or power that an entity currently has ready for use or deployment.
-
D.
strengthType
Indicates the specific category or nature of strength associated with an entity or relationship (e.g., physical, structural, or conceptual strength).
-
E.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
- F. None of above.
Provenance (1 batch)
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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:59 a.m.