Triple
T4808731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | honour |
E107010
|
entity |
| Predicate | canConflictWith |
P4897
|
FINISHED |
| Object | self-preservation |
—
|
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: self-preservation | Statement: [honour, canConflictWith, self-preservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canConflictWith Context triple: [honour, canConflictWith, self-preservation]
-
A.
conflictWith
chosen
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
B.
appliesToConflictWith
Indicates that one element’s scope, rules, or effects are relevant to a conflict involving another element, defining how that element is implicated in or governed by the conflict.
-
C.
namedForConflict
Indicates that one entity is named after, or in commemoration of, a specific conflict, war, or battle.
-
D.
usedInConflictType
Indicates that something (such as a resource, method, or capability) is employed or applied within a specific type or category of conflict.
-
E.
conflictRequirement
Indicates that one requirement is incompatible with or prevents the fulfillment of another requirement.
- 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_69bd43f779448190b92885cb70abb6c2 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1c43a48190a65e56b1624a2339 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.