Triple
T263450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fireside chats on banking crisis |
E5801
|
entity |
| Predicate | hasDateOfFirstBroadcast |
P2596
|
FINISHED |
| Object | 1933-03-12 |
—
|
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: 1933-03-12 | Statement: [Fireside chats on banking crisis, hasDateOfFirstBroadcast, 1933-03-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDateOfFirstBroadcast Context triple: [Fireside chats on banking crisis, hasDateOfFirstBroadcast, 1933-03-12]
-
A.
firstAired
chosen
Indicates the date on which something (such as a show, episode, or broadcast content) was first aired or publicly transmitted.
-
B.
originallyAiredOn
Indicates the date or time when a media work (such as a TV episode, radio show, or broadcast) was first publicly aired.
-
C.
firstTelevisionBroadcast
Indicates that the subject is the entity responsible for the earliest or inaugural television broadcast of the object.
-
D.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
E.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
- 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_69a258dd8ea08190ac554a1cc8dfd8c3 |
completed | Feb. 28, 2026, 2:54 a.m. |
| NER | Named-entity recognition | batch_69a25d8e809881908a58c9a4e3ba07c3 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.