Triple
T18916700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Jenkins |
E462741
|
entity |
| Predicate | politicalUseOfInjury |
P7603
|
FINISHED |
| Object | to justify war with Spain |
—
|
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: to justify war with Spain | Statement: [Robert Jenkins, politicalUseOfInjury, to justify war with Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalUseOfInjury Context triple: [Robert Jenkins, politicalUseOfInjury, to justify war with Spain]
-
A.
politicalUse
chosen
Indicates that something is used for political purposes, such as influencing, supporting, or opposing political actors, policies, or processes.
-
B.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
C.
injuriesApprox
Indicates an approximate or estimated number or extent of injuries associated with an event or entity.
-
D.
allegedInjury
Indicates that an injury is claimed or asserted to have occurred, typically without being legally or factually established.
-
E.
causeOfInjury
Indicates that one entity is the source or reason that another entity sustained an injury.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c627724881909cf63c67d64321e8 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.