Triple
T18533532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minx |
E452900
|
entity |
| Predicate | revivalAnnouncementDate |
P429
|
FINISHED |
| Object | 2023-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: 2023-01 | Statement: [Minx, revivalAnnouncementDate, 2023-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalAnnouncementDate Context triple: [Minx, revivalAnnouncementDate, 2023-01]
-
A.
revivalAnnouncedBy
Indicates that an entity’s revival (such as a show, event, or project being brought back) is publicly announced by a particular agent or source.
-
B.
announcementDate
chosen
Indicates the date on which an announcement is formally made or becomes publicly known.
-
C.
revivalEndTime
Indicates the point in time at which a revival process, event, or restored state comes to an end.
-
D.
announcedAt
Indicates that an announcement or declaration was made at a specific time or event.
-
E.
brandRevivalDate
Indicates the date on which a previously inactive or discontinued brand was brought back into use or relaunched.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533ffc38881909f8ee132314f58a3 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.