Triple
T11396108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Miss Brooks |
E269976
|
entity |
| Predicate | radioEndDate |
P50200
|
FINISHED |
| Object | 1957-02-27 |
—
|
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: 1957-02-27 | Statement: [Our Miss Brooks, radioEndDate, 1957-02-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioEndDate Context triple: [Our Miss Brooks, radioEndDate, 1957-02-27]
-
A.
radioAdaptationReleaseDate
Indicates the date on which a work’s adaptation for radio was first released or broadcast.
-
B.
broadcastEnded
chosen
Indicates that a previously active broadcast has finished and is no longer ongoing.
-
C.
radioAnnouncers
Indicates that one entity serves as a radio announcer for, or in association with, another entity.
-
D.
radioFormat
Indicates the specific type or style of radio programming or broadcast format associated with an entity.
-
E.
radioRestrictions
Indicates that there are specific limitations or rules governing the use or operation of radio communications between the related entities.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80019d3d48190a2f473deb6eae33a |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.