Triple
T31369978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altamont Speedway |
E800131
|
entity |
| Predicate | securityGroupAtConcert |
P182266
|
FINISHED |
| Object | Hells Angels |
—
|
NE NERFINISHED |
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: Hells Angels | Statement: [Altamont Speedway, securityGroupAtConcert, Hells Angels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityGroupAtConcert Context triple: [Altamont Speedway, securityGroupAtConcert, Hells Angels]
-
A.
audienceAccess
Indicates that one entity has permission or ability to access, view, or engage with a particular audience associated with another entity.
-
B.
associatedMusicAudience
Indicates a relationship where a piece of music, musical work, or performance is intended for, targeted at, or commonly associated with a particular audience or listener group.
-
C.
visitorManagement
Indicates the management, tracking, and control of visitors’ access, activities, and permissions within a location or system.
-
D.
sharesBandWith
Indicates that two entities are members of at least one of the same musical bands.
-
E.
groupTogether
Indicates that multiple entities are treated or arranged as a single collective unit or set.
- 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 29, 2026, 9:18 p.m.