Triple
T33503591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Catalan Way |
E858057
|
entity |
| Predicate | nonViolent |
P77882
|
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: [2013 Catalan Way, nonViolent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonViolent Context triple: [2013 Catalan Way, nonViolent, true]
-
A.
nonviolenceTypeDiscussed
Indicates that the discussion or communication centers on a particular type or form of nonviolence.
-
B.
employedNonviolence
chosen
Indicates that an entity used nonviolent methods or strategies, rather than physical force or aggression, to pursue its goals or resolve a conflict.
-
C.
nonConstructive
Indicates that the relationship or action does not provide a direct, explicit method or example to realize or build the object, outcome, or proof it asserts exists.
-
D.
nonVerbalIn
Indicates that an entity is present in a location or context without using spoken or written language, relying instead on non-verbal communication or behavior.
-
E.
nonDerogation
Indicates that the existence or exercise of one right, obligation, or provision does not diminish, restrict, or invalidate another.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e59dcc40819098acbe7224febc83 |
completed | May 3, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69f6e3db74c081909a991309d835d477 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.