Triple
T29283380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Nashville Waffle House shooting |
E742440
|
entity |
| Predicate | businessAffected |
P45127
|
FINISHED |
| Object | Waffle House |
E642299
|
NE 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: Waffle House | Statement: [2018 Nashville Waffle House shooting, businessAffected, Waffle House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessAffected Context triple: [2018 Nashville Waffle House shooting, businessAffected, Waffle House]
-
A.
impactOnBusiness
chosen
Indicates the effect or influence that one factor, event, or action has on a business’s performance, operations, or outcomes.
-
B.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
C.
business
Indicates that an entity is engaged in commercial or professional activities, such as providing goods or services for profit.
-
D.
businessFunction
Indicates the specific role, activity, or operational function that an entity performs within a business context.
-
E.
businessScale
Indicates the relative size or level of operations of a business, such as its scope, capacity, or market reach.
- F. None of above.
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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25a856fa208190a0141fbccbe92c46 |
completed | June 7, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 12:56 p.m.