Triple
T17218144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Unearthly Child |
E417903
|
entity |
| Predicate | broadcastLiveOrRecorded |
P126443
|
FINISHED |
| Object | pre-recorded |
—
|
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: pre-recorded | Statement: [An Unearthly Child, broadcastLiveOrRecorded, pre-recorded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastLiveOrRecorded Context triple: [An Unearthly Child, broadcastLiveOrRecorded, pre-recorded]
-
A.
broadcastLiveFrom
Indicates that an event or program is being transmitted in real time from a specific location or source.
-
B.
hasLiveBroadcast
Indicates that a live broadcast is currently being transmitted or available for the referenced entity.
-
C.
includesLiveRecordingFrom
Indicates that something contains or incorporates a live recording sourced from another entity.
-
D.
originallyBroadcastLive
Indicates that the content was transmitted to audiences in real time at the time of its first broadcast, rather than being pre-recorded.
-
E.
recordedAsLive
Indicates that an audio or video performance was captured in real time before an audience or in a live setting, rather than produced or edited in a studio environment.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddb2b148190b3b50572cc285e3d |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:38 a.m.