Triple
T31997979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Madness |
E817043
|
entity |
| Predicate | hasIntendedMessage |
P13485
|
FINISHED |
| Object | critique of militarism |
—
|
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: critique of militarism | Statement: [Military Madness, hasIntendedMessage, critique of militarism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntendedMessage Context triple: [Military Madness, hasIntendedMessage, critique of militarism]
-
A.
intendedMessage
chosen
Indicates that one entity is the message or content that another entity aims or plans to communicate.
-
B.
hasIntent
Indicates that an entity possesses a purpose, plan, or goal directing its actions or behavior toward a particular outcome.
-
C.
hasIntendedMedium
Indicates that an entity is associated with a medium or format it is designed, planned, or meant to be presented or communicated through.
-
D.
hasIntendedEffect
Indicates that one entity is expected or designed to produce a particular effect or outcome on another entity or context.
-
E.
hasMessageSender
Indicates that one entity is the sender or originator of a given message.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 1, 2026, 12:14 a.m.