Triple
T10712195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bound Brook |
E252564
|
entity |
| Predicate | forcesAmericanApproximate |
P77888
|
FINISHED |
| Object | 500 |
—
|
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: 500 | Statement: [Battle of Bound Brook, forcesAmericanApproximate, 500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcesAmericanApproximate Context triple: [Battle of Bound Brook, forcesAmericanApproximate, 500]
-
A.
forceTypeAmerican
chosen
Indicates that the force involved is of the American (United States) military or security type.
-
B.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
C.
inImperialSystemApprox
Indicates that a quantity is approximately expressed or measured in the imperial system of units rather than exactly or in another unit system.
-
D.
isOftenAmericanizedFormOf
Indicates that one term is a version of another term that has been adapted into common American usage, typically in spelling, form, or style.
-
E.
literalMeaningApproximation
Indicates that one entity expresses an approximate or rough literal meaning of another entity, rather than an exact or fully precise interpretation.
- 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.