Triple
T258448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Army Air Forces |
E5487
|
entity |
| Predicate | peakPersonnelStrength |
P3346
|
FINISHED |
| Object | over 2,000,000 |
—
|
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: over 2,000,000 | Statement: [United States Army Air Forces, peakPersonnelStrength, over 2,000,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPersonnelStrength Context triple: [United States Army Air Forces, peakPersonnelStrength, over 2,000,000]
-
A.
peakPersonnel
chosen
Indicates the maximum number of personnel involved or present at any point during a specified period or activity.
-
B.
collectionStrength
Indicates the degree or intensity of association or cohesion among items within a collection.
-
C.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
D.
strength
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
-
E.
peakStatus
Indicates the condition or phase of something at its highest or most intense point in its progression or lifecycle.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25f921c2881908821ca2c03815eae |
completed | Feb. 28, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69a25b6b3ea88190bbd858999e42efae |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.