Triple
T4319660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Warfare |
E96481
|
entity |
| Predicate | seeksToReduce |
P28788
|
FINISHED |
| Object | duplication of effort |
—
|
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: duplication of effort | Statement: [Joint Warfare, seeksToReduce, duplication of effort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeksToReduce Context triple: [Joint Warfare, seeksToReduce, duplication of effort]
-
A.
reduces
Indicates that one entity causes a decrease in the amount, intensity, degree, or impact of another entity.
-
B.
reducesTo
Indicates that one expression, structure, or state can be transformed or simplified into another, typically more basic or canonical, form.
-
C.
soughtTo
Indicates that one entity attempted or intended to obtain, achieve, or bring about another entity or outcome.
-
D.
aimedToLimit
chosen
Indicates an action or policy that was intentionally directed toward restricting, reducing, or constraining something.
-
E.
seeksToShape
Indicates an entity’s intention or effort to influence, mold, or determine the form, direction, or outcome of another entity or situation.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35112ec008190958487f501481887 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.