Triple
T33316910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMCharacteristicEvent |
E853038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | HMEvent subclass |
C1824
|
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: HMEvent subclass Context triple: [HMCharacteristicEvent, instanceOf, HMEvent subclass]
-
A.
event-handling framework
An event-handling framework is a software architecture that manages the registration, dispatch, and processing of events, enabling decoupled components to react to user actions, system changes, or messages in an organized and scalable way.
-
B.
event
chosen
An event is a distinct occurrence or happening, often bounded in time and space, that involves one or more participants and may trigger changes in state or behavior within a system.
-
C.
event complex
An event complex is a structured grouping of interrelated events that together form a coherent unit of activity, process, or occurrence within a system or domain.
-
D.
historic event
A historic event is a significant occurrence in the past that has had a lasting impact on societies, cultures, or the course of history.
-
E.
global broadcast event
A global broadcast event is a live or scheduled media transmission distributed simultaneously across multiple regions and platforms to reach a worldwide audience in real time.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:33 a.m.