Triple
T23798106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brighten |
E588591
|
entity |
| Predicate | followsWorkReleaseYear |
P66026
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Brighten, followsWorkReleaseYear, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsWorkReleaseYear Context triple: [Brighten, followsWorkReleaseYear, 1998]
-
A.
followsSingleReleaseYear
chosen
Indicates that one entity is released in the year immediately following the release year of another single.
-
B.
previousWorkReleaseYear
Indicates the year in which an earlier or prior work in a sequence or related set was released.
-
C.
basedInWorkReleaseYear
Indicates that an entity is based in, or derived from, a work that was released in a specified year.
-
D.
followedByReleaseYear
Indicates that one item is immediately succeeded by another item in terms of release year.
-
E.
workReleaseYear
Indicates the calendar year in which a work (such as a book, film, or album) was first released or made publicly available.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6dea2888190b3ff1c96da5cfefb |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:50 p.m.