Triple
T11779076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubbardton engagement |
E280092
|
entity |
| Predicate | armedForcesBranchInvolved |
P97149
|
FINISHED |
| Object | infantry |
—
|
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: infantry | Statement: [Hubbardton engagement, armedForcesBranchInvolved, infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedForcesBranchInvolved Context triple: [Hubbardton engagement, armedForcesBranchInvolved, infantry]
-
A.
armedForcesInvolved
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
B.
armedForcesBranchContext
chosen
Indicates the specific branch of a nation's armed forces within which a given military-related fact, role, or activity is situated.
-
C.
militaryBranchOfGovernment
Indicates that a military organization functions as an official branch or component of a government.
-
D.
armedForcesBranchNumber
Indicates the specific numerical designation or identifier assigned to a branch of the armed forces within a military organization.
-
E.
militaryBranchAssociatedWith
Indicates a relationship where an entity is connected to, or operates as part of, a specific branch of a military organization.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:42 p.m.