Triple
T38266313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overexposed |
E1021067
|
entity |
| Predicate | deluxeEdition |
P53740
|
FINISHED |
| Object | Overexposed (deluxe edition) |
—
|
NE NERFINISHED |
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: Overexposed (deluxe edition) | Statement: [Overexposed, deluxeEdition, Overexposed (deluxe edition)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deluxeEdition Context triple: [Overexposed, deluxeEdition, Overexposed (deluxe edition)]
-
A.
deluxeEditionReleaseDate
Indicates the date on which a deluxe edition of a work is officially released.
-
B.
deluxeEditionReleaseYear
Indicates the year in which a deluxe edition of a work (such as an album, book, or film) was released.
-
C.
hasDeluxeEdition
chosen
Indicates that an entity has an associated deluxe or enhanced edition version of itself.
-
D.
hasDeluxeEditionTrackCount
Indicates the number of tracks included in the deluxe edition of a given release or work.
-
E.
expandedEditionIncludes
Indicates that an expanded edition of a work contains, as part of its content, the material from another specified edition or version.
- 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.