Triple
T20305102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Brigade |
E505587
|
entity |
| Predicate | casualtyRate |
P139600
|
FINISHED |
| Object | among highest in Confederate 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: among highest in Confederate Army | Statement: [Texas Brigade, casualtyRate, among highest in Confederate Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtyRate Context triple: [Texas Brigade, casualtyRate, among highest in Confederate Army]
-
A.
mortalityRate
Indicates the proportion of individuals in a defined population that die within a specified time period.
-
B.
casualtiesInflictedOn
Indicates that one party has caused deaths or injuries to another party as a result of a harmful event or action.
-
C.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
D.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
E.
battleCasualty
Indicates that an entity was killed, wounded, or otherwise harmed as a direct result of a specific battle or armed conflict.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6773f8f688190b616f972b9bbb28e |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:18 a.m.