Triple
T4868901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Don't Know How It Feels |
E109037
|
entity |
| Predicate | radioEditFeature |
P25064
|
FINISHED |
| Object | backmasked word "joint" |
—
|
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: backmasked word "joint" | Statement: [You Don't Know How It Feels, radioEditFeature, backmasked word "joint"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioEditFeature Context triple: [You Don't Know How It Feels, radioEditFeature, backmasked word "joint"]
-
A.
hasRadioEdit
chosen
Indicates that an entity has an associated radio-friendly edited version of itself.
-
B.
radioFormat
Indicates the specific type or style of radio programming or broadcast format associated with an entity.
-
C.
radioInterface
Indicates a relationship where one entity provides or defines the radio communication interface used by another entity for wireless connectivity or control.
-
D.
radioAdaptationDirector
Indicates that the subject served as the director of a radio adaptation of the object work or production.
-
E.
hasRadioBroadcasts
Indicates that one entity transmits or provides content via radio broadcasts to another entity or audience.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c28e56081908ee411ac94c3769e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.