Triple
T22179412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guantanamera |
E548128
|
entity |
| Predicate | hasBroadcastOrigin |
P147274
|
FINISHED |
| Object | Cuban radio |
—
|
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: Cuban radio | Statement: [Guantanamera, hasBroadcastOrigin, Cuban radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadcastOrigin Context triple: [Guantanamera, hasBroadcastOrigin, Cuban radio]
-
A.
hasBroadcastScope
Indicates that a broadcast is intended to reach a specified scope or range of recipients, areas, or contexts.
-
B.
hasBroadcastContext
Indicates that a broadcast is associated with a particular contextual setting, such as circumstances, environment, or conditions under which it is transmitted or received.
-
C.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
-
D.
hasBroadcastStatus
Indicates the current broadcast-related state or condition of an item, such as whether it is scheduled, live, completed, or unavailable.
-
E.
hasBroadcastService
Indicates that an entity provides or is associated with a particular broadcast service.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa3af308190bbddadfa3066f850 |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:34 p.m.