Triple
T10712196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bound Brook |
E252564
|
entity |
| Predicate | forcesBritishHessianApproximate |
P40540
|
FINISHED |
| Object | 4000 |
—
|
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: 4000 | Statement: [Battle of Bound Brook, forcesBritishHessianApproximate, 4000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcesBritishHessianApproximate Context triple: [Battle of Bound Brook, forcesBritishHessianApproximate, 4000]
-
A.
strengthBritishForces
chosen
Indicates the numerical size or combat capacity of British military forces in a given context or operation.
-
B.
approximateStrengthFrancoBavarian
Indicates an estimated or inferred degree of strength or intensity in the Franco-Bavarian relationship or interaction.
-
C.
militaryForceInvolved (British)
Indicates that the British military forces participated in or were involved in the referenced event or action.
-
D.
strength_British_side
Indicates the level or measure of military or strategic power possessed by the British side in a given context.
-
E.
approximateGallicStrength
Indicates an estimation or rough calculation of the level or magnitude of Gallic strength in a given 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fe533ec081909eafab85f6f6d6b9 |
completed | April 9, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.