Triple
T28318890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stompa |
E717218
|
entity |
| Predicate | hasRadioSuccess |
P130412
|
FINISHED |
| Object | widespread |
—
|
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: widespread | Statement: [Stompa, hasRadioSuccess, widespread]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadioSuccess Context triple: [Stompa, hasRadioSuccess, widespread]
-
A.
radioSuccess
chosen
Indicates that an entity has achieved success or favorable outcomes in the context of radio broadcasting or radio-related activities.
-
B.
hasRadio
Indicates that an entity is equipped with or includes a radio device.
-
C.
hasRadioPresence
Indicates that an entity maintains a detectable or active presence in radio broadcasts or radio communication channels.
-
D.
hasRadioVersion
Indicates that one entity is a radio-edit or radio-specific version of another entity.
-
E.
radioFormatSuccess
Indicates that a particular radio format or programming approach has achieved success, such as strong performance or positive outcomes.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 28, 2026, 12:23 a.m.