Triple
T23699587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack McFarland |
E585552
|
entity |
| Predicate | revivalFirstAppearanceYear |
P153441
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Jack McFarland, revivalFirstAppearanceYear, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalFirstAppearanceYear Context triple: [Jack McFarland, revivalFirstAppearanceYear, 2017]
-
A.
revivalYear
Indicates the year in which something (such as a work, practice, or institution) was brought back into active use or renewed after a period of decline or inactivity.
-
B.
revivalOriginalReleaseStart
Indicates the date or point in time when the original release associated with a later revival first began.
-
C.
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.
-
D.
revivedInDecade
Indicates that an entity was brought back into use, popularity, or active existence during a specified decade.
-
E.
revivalAiredOnChannel
Indicates that a revival of a show or series was broadcast on a specific television channel.
- F. None of above. chosen
Provenance (4 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b681a93c8190b8dab12e7f0aa6fd |
completed | April 29, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f157cc43a881909ed2d8b0a09b5d73 |
completed | April 29, 2026, 12:58 a.m. |
Created at: April 17, 2026, 6:53 p.m.