Triple
T9955727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian People’s Army |
E195441
|
entity |
| Predicate | peakStrengthApprox |
P2981
|
FINISHED |
| Object | 100000–150000 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: 100000–150000 personnel | Statement: [Hungarian People’s Army, peakStrengthApprox, 100000–150000 personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakStrengthApprox Context triple: [Hungarian People’s Army, peakStrengthApprox, 100000–150000 personnel]
-
A.
peakApproximateMa
Indicates that one entity’s peak value is approximately equal to another entity’s peak value.
-
B.
peakRating
Indicates the highest rating value that has been achieved or recorded for an entity over a given period or context.
-
C.
strengthPeak
Indicates the point or period at which an entity’s strength reaches its maximum level.
-
D.
strengthDescription
Indicates a description or characterization of the degree of strength associated with an entity or relationship.
-
E.
estimatedStrength
chosen
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb69631d08190ab2b1d1c22d46da7 |
completed | April 2, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:46 p.m.