Triple
T5326819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Jacinto Battlefield |
E123205
|
entity |
| Predicate | battleCasualtiesTexian |
P34187
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [San Jacinto Battlefield, battleCasualtiesTexian, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleCasualtiesTexian Context triple: [San Jacinto Battlefield, battleCasualtiesTexian, low]
-
A.
casualtiesTexianKilled
chosen
Indicates that the relationship specifies the number of Texian individuals who were killed as casualties in a particular event or conflict.
-
B.
confederateCasualtiesAndLosses
Indicates the number or extent of casualties and material losses suffered by Confederate forces in a conflict or engagement.
-
C.
casualtiesMexicanKilled
Indicates that the event or action resulted in Mexican individuals being killed as casualties.
-
D.
roleInMexicanAmericanWar
Indicates that an entity participated in the Mexican–American War in a specified capacity or function.
-
E.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84561c7081909e5937c7816e492c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.