Triple
T33751330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTP |
E864847
|
entity |
| Predicate | beganRadioBroadcastsUnderCurrentStructure |
P116542
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [RTP, beganRadioBroadcastsUnderCurrentStructure, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganRadioBroadcastsUnderCurrentStructure Context triple: [RTP, beganRadioBroadcastsUnderCurrentStructure, 1970s]
-
A.
broadcastBegan
Indicates that the transmission or airing of a broadcast has started.
-
B.
broadcastingUseBegan
chosen
Indicates that the use of a broadcasting service or capability has started at a specific point in time.
-
C.
broadcastService
Indicates that one entity provides or is associated with a broadcast service used to distribute media or information to an audience.
-
D.
broadcastsIn
Indicates that one entity transmits or airs content within a particular medium, channel, location, or time frame.
-
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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.