Triple
T1050422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beveridge Report |
E22684
|
entity |
| Predicate | aimedToCombat |
P19801
|
FINISHED |
| Object | want |
—
|
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: want | Statement: [Beveridge Report, aimedToCombat, want]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedToCombat Context triple: [Beveridge Report, aimedToCombat, want]
-
A.
aimsToProtect
Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
-
B.
aimsToSolve
chosen
Indicates an intention or purpose directed toward resolving, addressing, or eliminating a particular problem, challenge, or issue.
-
C.
warAim
Indicates the strategic objective or intended outcome that a party seeks to achieve through engaging in war or armed conflict.
-
D.
coordinatedAttacksAlsoTargeted
Indicates that in a set of coordinated attacks, the same target was also attacked as part of those coordinated actions.
-
E.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8b40d50819091cb37a2236e82ee |
completed | March 1, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69a4b7309cc481908ed839b0b8d75dbf |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.