Triple
T12391008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Chang |
E295991
|
entity |
| Predicate | viewsOnWar |
P33446
|
FINISHED |
| Object | embraces war as honorable and desirable |
—
|
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: embraces war as honorable and desirable | Statement: [General Chang, viewsOnWar, embraces war as honorable and desirable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsOnWar Context triple: [General Chang, viewsOnWar, embraces war as honorable and desirable]
-
A.
viewOnWar
chosen
Indicates a stance, opinion, or perspective that an entity holds regarding war or armed conflict.
-
B.
militaryConflictView
Indicates a perspective, interpretation, or representation of a specific military conflict or battle.
-
C.
viewsMilitaryAs
Indicates that one entity holds a particular perception, attitude, or evaluative stance toward the military as an institution or concept.
-
D.
viewOnUniversalPeace
Indicates a stance, perspective, or opinion that an entity holds regarding the concept or ideal of universal peace.
-
E.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fd0bcc48190bb1a59a3aaa6bfdf |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.