Triple
T3105248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anti-Machiavel |
E64814
|
entity |
| Predicate | viewOfWar |
P33446
|
FINISHED |
| Object | war should be limited and defensive |
—
|
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: war should be limited and defensive | Statement: [Anti-Machiavel, viewOfWar, war should be limited and defensive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOfWar Context triple: [Anti-Machiavel, viewOfWar, war should be limited and defensive]
-
A.
viewOnWar
chosen
Indicates a stance, opinion, or perspective that an entity holds regarding war or armed conflict.
-
B.
theaterOfWar
Indicates that a specified location or region is the primary area where a particular conflict, war, or military operation takes place.
-
C.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
-
D.
warFrontDepicted
Indicates that a particular war front or battlefield area is visually represented or shown in a depiction.
-
E.
warDepicted
Indicates that a work or representation portrays, illustrates, or otherwise depicts a particular war or armed conflict.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29a90e88190afb8a10291ef1946 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.