Triple
T22131522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stinkfist |
E546913
|
entity |
| Predicate | radioTitleReason |
P15925
|
FINISHED |
| Object | to avoid controversy over the word "Stinkfist" |
—
|
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: to avoid controversy over the word "Stinkfist" | Statement: [Stinkfist, radioTitleReason, to avoid controversy over the word "Stinkfist"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioTitleReason Context triple: [Stinkfist, radioTitleReason, to avoid controversy over the word "Stinkfist"]
-
A.
reasonForTitle
chosen
Indicates the justification, cause, or basis for assigning a particular title to an entity.
-
B.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
C.
ringPresentationReason
Indicates the reason or occasion for which a ring is being presented or given.
-
D.
byElectionReason
Indicates the reason or cause for which a by-election is being held.
-
E.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1298746888190967b4e3ae0558e9e |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.