Triple
T5116535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bloody Marsh |
E115348
|
entity |
| Predicate | armedForcesType |
P39448
|
FINISHED |
| Object | British regulars |
—
|
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: British regulars | Statement: [Battle of Bloody Marsh, armedForcesType, British regulars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedForcesType Context triple: [Battle of Bloody Marsh, armedForcesType, British regulars]
-
A.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
B.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
-
C.
groundForces
Indicates that one entity deploys, commands, or involves military forces operating on land in relation to another entity or context.
-
D.
armedForcesInvolved
chosen
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
E.
USForceType
Indicates the type or category of U.S. military force involved in a given relationship or action.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75cfa9f88190aa7dfd264e554899 |
completed | March 20, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69bd7160d44081908cc64f3c14d28b81 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.