Triple
T19010323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steak and Ale |
E465204
|
entity |
| Predicate | brandRevivalAnnounced |
P126060
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Steak and Ale, brandRevivalAnnounced, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandRevivalAnnounced Context triple: [Steak and Ale, brandRevivalAnnounced, 2022]
-
A.
brandRevival
Indicates the process or action of restoring a declining or dormant brand to renewed strength, relevance, and market presence.
-
B.
brandRevivedBy
Indicates that a previously inactive, discontinued, or defunct brand has been brought back into use or reintroduced by a specific agent or entity.
-
C.
brandRevivalDate
chosen
Indicates the date on which a previously inactive or discontinued brand was brought back into use or relaunched.
-
D.
brandLaunch
Indicates the event or action of introducing a new brand (or a major rebranding) into the market.
-
E.
announcedRebrandingAs
Indicates that one entity has publicly declared it will change its name, brand, or identity to that of another entity.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6a8225c81908e80ae7eb1c1301b |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.