Triple
T37041129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chex Quest 3 |
E916782
|
entity |
| Predicate | isNonViolent |
P187271
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chex Quest 3, isNonViolent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonViolent Context triple: [Chex Quest 3, isNonViolent, true]
-
A.
employedNonviolence
Indicates that an entity used nonviolent methods or strategies, rather than physical force or aggression, to pursue its goals or resolve a conflict.
-
B.
nonviolenceTypeDiscussed
Indicates that the discussion or communication centers on a particular type or form of nonviolence.
-
C.
justifiesViolenceThrough
Indicates that one party legitimizes or defends the use of violence by appealing to, or reasoning through, another factor, belief, or circumstance.
-
D.
containsViolence
Indicates that the subject includes, depicts, or involves acts of physical harm, aggression, or violent behavior.
-
E.
violenceLevel
Indicates the degree or intensity of violent behavior, actions, or content present in or associated with an entity.
- F. None of above. chosen
Provenance (4 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb34e4906c8190abb1c293fb84329a |
completed | May 6, 2026, 12:32 p.m. |
Created at: May 3, 2026, 4:14 p.m.