Triple
T31370096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Hells Angels were paid in beer" |
E800135
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical event description |
C27133
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical event description Context triple: ["Hells Angels were paid in beer", instanceOf, historical event description]
-
A.
historic event
chosen
A historic event is a significant occurrence in the past that has had a lasting impact on societies, cultures, or the course of history.
-
B.
historical event name
A historical event name is a concise label used to identify and refer to a specific significant occurrence in the past, often reflecting its time, place, or defining characteristics.
-
C.
historical event collection
A historical event collection is an organized set of documented occurrences from the past, grouped and structured to support analysis, comparison, and retrieval based on time, place, theme, or significance.
-
D.
event in ancient history
An event in ancient history is a significant occurrence or series of actions that took place in early human civilizations and has had a lasting impact on cultural, political, or social development.
-
E.
pair of historical events
A pair of historical events is a conceptual grouping of two distinct occurrences from the past that are related by time, cause, theme, or contrast for purposes of comparison or analysis.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 29, 2026, 9:18 p.m.