Triple
T23040490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pancho Villa's raid on Columbus, New Mexico |
E573719
|
entity |
| Predicate | killedAmongRaiders |
P4707
|
FINISHED |
| Object | dozens of Villista fighters |
—
|
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: dozens of Villista fighters | Statement: [Pancho Villa's raid on Columbus, New Mexico, killedAmongRaiders, dozens of Villista fighters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killedAmongRaiders Context triple: [Pancho Villa's raid on Columbus, New Mexico, killedAmongRaiders, dozens of Villista fighters]
-
A.
killedBy
Indicates that one entity caused the death of another entity.
-
B.
killedNear
Indicates that one entity killed another in close spatial proximity to a specified location or reference point.
-
C.
killedOrCaptured
Indicates that one entity has either killed or taken another entity into custody or control.
-
D.
killedOrMortallyWounded
Indicates that one entity caused the death of, or inflicted injuries certain to result in the death of, another entity.
-
E.
killedDuring
chosen
Indicates that one entity caused the death of another entity in the course of, or as part of, a specified event or time period.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18512df708190a6892e743a289c74 |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:53 p.m.