Triple
T35342617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Mesa |
E1020642
|
entity |
| Predicate | primaryU.S.ForceType |
P3860
|
FINISHED |
| Object | artillery and volunteer troops |
—
|
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: artillery and volunteer troops | Statement: [Battle of the Mesa, primaryU.S.ForceType, artillery and volunteer troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryU.S.ForceType Context triple: [Battle of the Mesa, primaryU.S.ForceType, artillery and volunteer troops]
-
A.
primaryUSForces
chosen
Indicates that the referenced forces constitute the main or principal contingent of United States military forces in a given context or operation.
-
B.
USForceType
Indicates the type or category of U.S. military force involved in a given relationship or action.
-
C.
USForceName
Indicates that the predicate specifies the official name or designation of a United States military force.
-
D.
USForces
Indicates the presence, involvement, or deployment of United States military forces in relation to a specified location, event, or entity.
-
E.
USForceStrength
Indicates the level or magnitude of military forces deployed or available by the United States 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.