Triple
T31301678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Did Something Bad |
E798228
|
entity |
| Predicate | hasExplicitAttitude |
P27747
|
FINISHED |
| Object | defiance |
—
|
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: defiance | Statement: [I Did Something Bad, hasExplicitAttitude, defiance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExplicitAttitude Context triple: [I Did Something Bad, hasExplicitAttitude, defiance]
-
A.
hasUserAttitude
chosen
Indicates that one entity holds a particular attitude, opinion, or evaluative stance toward another entity or subject.
-
B.
isExplicit
Indicates that something is stated clearly and directly, leaving no room for ambiguity or implied interpretation.
-
C.
hasCommunityAttitude
Indicates that a community holds a particular stance, opinion, or disposition toward a given entity or situation.
-
D.
hasExplicitInterpretation
Indicates that something is associated with a clearly defined and unambiguous meaning or interpretation.
-
E.
hasSentiment
Indicates that one entity expresses or embodies a particular emotional attitude, evaluation, or sentiment toward another entity or subject.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 29, 2026, 9:14 p.m.