Triple
T15732189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Afterparty |
E381370
|
entity |
| Predicate | settingOfSeason1 |
P119973
|
FINISHED |
| Object | high school reunion afterparty |
—
|
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: high school reunion afterparty | Statement: [The Afterparty, settingOfSeason1, high school reunion afterparty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfSeason1 Context triple: [The Afterparty, settingOfSeason1, high school reunion afterparty]
-
A.
firstSeasonSettingYear
Indicates the calendar year in which the first season of something (such as a series or competition) is set.
-
B.
startSeason
Indicates the point in time or event at which a particular season begins.
-
C.
adaptationSeason
Indicates that one work is an adaptation of another specifically for a particular season or installment in a series.
-
D.
firstSeasonDetermined
Indicates that the initial season associated with an entity has been identified or established.
-
E.
firstSeasonBasedOn
Indicates that the first season of a series is based on, adapted from, or derived from another work or source.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fd3614481908b2694b1d3550058 |
completed | April 16, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0094af5b481908ad51d5d7ba0c726 |
completed | April 15, 2026, 9:55 p.m. |
Created at: April 10, 2026, 4:46 a.m.