Triple
T19767299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobite army under Charles Edward Stuart |
E474790
|
entity |
| Predicate | approximatePeakStrength |
P2981
|
FINISHED |
| Object | about 9,000 men |
—
|
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: about 9,000 men | Statement: [Jacobite army under Charles Edward Stuart, approximatePeakStrength, about 9,000 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximatePeakStrength Context triple: [Jacobite army under Charles Edward Stuart, approximatePeakStrength, about 9,000 men]
-
A.
approximateUserPeak
Indicates that one value or event is an estimated or inferred maximum point associated with a particular user.
-
B.
estimatedStrength
chosen
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
-
C.
peakApproximateMa
Indicates that one entity’s peak value is approximately equal to another entity’s peak value.
-
D.
strengthPeak
Indicates the point or period at which an entity’s strength reaches its maximum level.
-
E.
approximateEnemyStrength
Indicates estimating the opposing side’s combat capabilities or power level, typically based on available but potentially incomplete information.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65358fc3c8190867fea2a2c4e7594 |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.