Triple
T21723418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shake Ya Ass |
E536216
|
entity |
| Predicate | radioVersionType |
P145097
|
FINISHED |
| Object | clean edit |
—
|
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: clean edit | Statement: [Shake Ya Ass, radioVersionType, clean edit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioVersionType Context triple: [Shake Ya Ass, radioVersionType, clean edit]
-
A.
radioServiceType
Indicates the specific category or kind of radio service associated with or provided by an entity.
-
B.
radioSystem
Indicates that one entity functions as, or is equipped with, a radio communication system used for transmitting and/or receiving signals.
-
C.
radioFormat
Indicates the specific type or style of radio programming or broadcast format associated with an entity.
-
D.
radioInterface
Indicates a relationship where one entity provides or defines the radio communication interface used by another entity for wireless connectivity or control.
-
E.
radioEmission
Indicates that one entity emits or produces radio-frequency radiation detectable as radio waves.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd97150c08190861bdc35416665a9 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:48 p.m.