Triple
T6814287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parks and Recreation |
E156712
|
entity |
| Predicate | specialEpisodeAirDate |
P73227
|
FINISHED |
| Object | 2020-04-30 |
—
|
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: 2020-04-30 | Statement: [Parks and Recreation, specialEpisodeAirDate, 2020-04-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialEpisodeAirDate Context triple: [Parks and Recreation, specialEpisodeAirDate, 2020-04-30]
-
A.
airdateDetail
Indicates the specific broadcast scheduling information for something, such as its original air date, time, or related airing details.
-
B.
specialBroadcasts
Indicates that one entity transmits or airs a broadcast that is designated as special or exceptional in some way to another entity or audience.
-
C.
associatedEpisode
Indicates that one entity is linked or connected to a particular episode as its related or relevant installment.
-
D.
includesSpecialEpisodes
Indicates that the subject collection or series contains one or more special, non-regular episodes.
-
E.
notableEpisode
Indicates that a particular episode is especially significant, memorable, or noteworthy in relation to the subject.
- 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_69c68828b26c819090fe9df7612bbc27 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d32c40508190932718a649fc1417 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:17 p.m.