Triple
T18983307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Top Boy |
E464484
|
entity |
| Predicate | revivalReleaseStart |
P7739
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Top Boy, revivalReleaseStart, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalReleaseStart Context triple: [Top Boy, revivalReleaseStart, 2019]
-
A.
revivalRunStart
chosen
Indicates the point in time or event at which a revival process or renewed operation begins.
-
B.
revivalOriginalReleaseStart
Indicates the date or point in time when the original release associated with a later revival first began.
-
C.
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.
-
D.
revivalVersionChartedOn
Indicates that a particular revival version of a work is recorded as having appeared on a specific chart.
-
E.
revivalVersionProducedFor
Indicates that a specific version of a revived work (such as a reboot, remake, or updated edition) was produced for a particular entity, context, or release.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d65de6288190a53a3fdd59013d2d |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.