Triple
T15051027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cork City Gaol |
E379359
|
entity |
| Predicate | broadcastingUseEnded |
P116543
|
FINISHED |
| Object | 19500s |
—
|
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: 19500s | Statement: [Cork City Gaol, broadcastingUseEnded, 19500s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastingUseEnded Context triple: [Cork City Gaol, broadcastingUseEnded, 19500s]
-
A.
broadcastEnded
Indicates that a previously active broadcast has finished and is no longer ongoing.
-
B.
broadcastBegan
Indicates that the transmission or airing of a broadcast has started.
-
C.
wasBroadcastOn
Indicates that a media item (such as a program, episode, or event) was transmitted or aired via a particular broadcast channel, station, or network.
-
D.
broadcastStatus
Indicates the current state or phase of a broadcast (e.g., scheduled, live, paused, or completed) in relation to the entities involved.
-
E.
broadcastRuntime
Indicates that an entity transmits or distributes content or data during its execution period or operational timeframe.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda90b9948190a0d71de0b23188da |
completed | April 15, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 3:01 a.m.