Triple
T1408757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Times |
E31755
|
entity |
| Predicate | endReleaseDate |
P9407
|
FINISHED |
| Object | 1979-08-01 |
—
|
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: 1979-08-01 | Statement: [Good Times, endReleaseDate, 1979-08-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endReleaseDate Context triple: [Good Times, endReleaseDate, 1979-08-01]
-
A.
finalReleaseYear
Indicates the calendar year in which something (such as a product, work, or version) is officially released for the last time.
-
B.
latestReleaseDate
chosen
Indicates the date on which the most recent version or release of an entity became available.
-
C.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
D.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
E.
releasedFor
Indicates that something has been made available or authorized for public use, distribution, or access.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3c10f44819085e1c4601423740d |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.