Triple
T19687181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Heights Bar |
E472740
|
entity |
| Predicate | hasNotableTypeOfEvent |
P14526
|
FINISHED |
| Object | sectarian attack |
—
|
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: sectarian attack | Statement: [The Heights Bar, hasNotableTypeOfEvent, sectarian attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTypeOfEvent Context triple: [The Heights Bar, hasNotableTypeOfEvent, sectarian attack]
-
A.
hasEventType
chosen
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
B.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
C.
hasNotablePersonEvent
Indicates that there exists a significant event in which the person plays a notable or central role.
-
D.
hasNotableEventName
Indicates that an entity is associated with a notable event identified by a specific name.
-
E.
hasRegularEventType
Indicates that an entity is associated with a recurring or routinely scheduled type of event.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420d39688190ad3a84dbffce4ffe |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.