Triple
T1940795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of San Jacinto |
E41547
|
entity |
| Predicate | casualtiesMexicanKilled |
P34188
|
FINISHED |
| Object | several hundred |
—
|
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: several hundred | Statement: [Battle of San Jacinto, casualtiesMexicanKilled, several hundred]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesMexicanKilled Context triple: [Battle of San Jacinto, casualtiesMexicanKilled, several hundred]
-
A.
CubanCasualtiesKilled
Indicates that Cuban individuals were killed as casualties in a specific event or conflict.
-
B.
casualtiesKilledUS
Indicates that the relationship specifies the number of U.S. individuals who were killed as casualties in an event or incident.
-
C.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
D.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
E.
deathTollEstimate
Indicates an estimated number of deaths attributed to a particular event, cause, or period.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb32a8d548190a231c7c2ce276a5e |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:36 p.m.