Triple
T8761948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sailor’s Creek |
E208222
|
entity |
| Predicate | approximateUnionStrength |
P26187
|
FINISHED |
| Object | about 26,000 |
—
|
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 26,000 | Statement: [Battle of Sailor’s Creek, approximateUnionStrength, about 26,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateUnionStrength Context triple: [Battle of Sailor’s Creek, approximateUnionStrength, about 26,000]
-
A.
unionStrengthApproximate
chosen
Indicates that the strength of a union or combination between entities is represented in an estimated or approximate manner rather than as an exact value.
-
B.
unionStrength
Indicates the degree of solidarity, cohesion, or collective power within or among unions or union members.
-
C.
estimatedStrength
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
-
D.
unionForces
Indicates that multiple forces are combined into a single, unified force acting together.
-
E.
UnionForcesStrength
Indicates the level or magnitude of military power possessed by Union forces 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dfa9d6c81908c4c6b3a6f84f67d |
completed | March 31, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.