Triple
T33108051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Prairie |
E847245
|
entity |
| Predicate | TexianForceType |
P176114
|
FINISHED |
| Object | volunteer army |
—
|
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: volunteer army | Statement: [Battle of the Prairie, TexianForceType, volunteer army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TexianForceType Context triple: [Battle of the Prairie, TexianForceType, volunteer army]
-
A.
enemyForceType
Indicates that one entity is characterized as a hostile or opposing force of a specified type relative to another entity.
-
B.
TexianCommander
Indicates that an entity serves as a military commander for Texian forces in a given context or event.
-
C.
patriotForceType
Indicates the type or category of force associated with a patriot or patriotic group (e.g., military, paramilitary, civilian).
-
D.
USForceType
Indicates the type or category of U.S. military force involved in a given relationship or action.
-
E.
UnionForcesType
Indicates that one entity is associated with, composed of, or characterized by a specific type or category of union forces.
- F. None of above. chosen
Provenance (4 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:26 a.m.