Triple
T38631564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seth Thornton |
E937467
|
entity |
| Predicate | wasAmbushedBy |
P174895
|
FINISHED |
| Object | Mexican forces |
—
|
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: Mexican forces | Statement: [Seth Thornton, wasAmbushedBy, Mexican forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAmbushedBy Context triple: [Seth Thornton, wasAmbushedBy, Mexican forces]
-
A.
ambushParticipant
chosen
Indicates that an entity takes part in an ambush, either as an attacker or as a target within that ambush event.
-
B.
wasAttackedIn
Indicates that an entity experienced an attack that occurred at or within a specified location or context.
-
C.
wasBesiegedBy
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
-
D.
killedInAttack
Indicates that an entity died as a direct result of a specific attack event.
-
E.
ambushStrategy
Indicates a planned tactic in which one party conceals its presence or intentions to surprise and attack another party.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.