Triple
T21919076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambush at Vado del Yeso |
E541253
|
entity |
| Predicate | governmentForceType |
P35582
|
FINISHED |
| Object | regular army troops |
—
|
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: regular army troops | Statement: [Ambush at Vado del Yeso, governmentForceType, regular army troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentForceType Context triple: [Ambush at Vado del Yeso, governmentForceType, regular army troops]
-
A.
typeOfGovernmentForces
chosen
Indicates the specific kind or classification of government-controlled military or security forces involved in a situation or context.
-
B.
strengthGovernmentForces
Indicates the level or degree of military or coercive power held or exerted by government forces in a given context.
-
C.
defenseOrganization
Indicates a relationship where an entity functions as an organization responsible for defense or military-related activities for another entity or jurisdiction.
-
D.
USForceType
Indicates the type or category of U.S. military force involved in a given relationship or action.
-
E.
defenseForces
Indicates a relationship where one entity serves as the military or protective force responsible for defending another entity.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12339d88881909e726c9b081bd177 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:44 p.m.