Triple
T31301674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Did Something Bad |
E798228
|
entity |
| Predicate | hasReputationEraStyle |
P162004
|
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: [I Did Something Bad, hasReputationEraStyle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReputationEraStyle Context triple: [I Did Something Bad, hasReputationEraStyle, true]
-
A.
hasEraInfluence
Indicates that one era or time period has a significant impact on shaping the characteristics, developments, or outcomes of another.
-
B.
hasEraTheme
chosen
Indicates that something is associated with, characterized by, or themed around a particular historical or cultural era.
-
C.
subjectHasEra
Indicates that a subject is associated with, defined by, or belongs to a particular historical or temporal era.
-
D.
hasEraSignificance
Indicates that something holds notable importance, influence, or relevance within a particular historical era or time period.
-
E.
isBsideOfEra
Indicates that one entity is the B-side counterpart associated with a particular era of another entity (such as a primary release or period).
- 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_6a01289f781481908f3788f8a719f2f4 |
completed | May 11, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a012823c7248190961e20be48dd6246 |
completed | May 11, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:14 p.m.