Triple
T10499721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Battle of Newbury |
E247637
|
entity |
| Predicate | royalistForceStrength |
P20427
|
FINISHED |
| Object | approximately 10,000–12,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: approximately 10,000–12,000 men | Statement: [First Battle of Newbury, royalistForceStrength, approximately 10,000–12,000 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalistForceStrength Context triple: [First Battle of Newbury, royalistForceStrength, approximately 10,000–12,000 men]
-
A.
RoyalistForceStrength
chosen
Indicates the size or level of military power possessed by a royalist-aligned force in a given context.
-
B.
royalistForcesIncluded
Indicates that the composition of the royalist forces included the specified entity or group.
-
C.
royalistObjective
Indicates that an entity’s goal, purpose, or intended outcome is to support, preserve, or advance a monarchy or royal authority.
-
D.
RoyalistArmyOutcome
Indicates the result or consequence experienced by the Royalist army in a particular conflict or event.
-
E.
RoyalistSide
Indicates that an entity is aligned with, supports, or belongs to the faction favoring a monarchy or royal authority in a given conflict 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098ef57c8190a9803c2c1736d299 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.