Triple
T33436121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Window |
E856241
|
entity |
| Predicate | hasEventHandlerProperties |
P146325
|
FINISHED |
| Object | onload |
—
|
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: onload | Statement: [Window, hasEventHandlerProperties, onload]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventHandlerProperties Context triple: [Window, hasEventHandlerProperties, onload]
-
A.
hasEventHandler
chosen
Indicates that one entity is responsible for handling or responding to events triggered by another entity.
-
B.
hasHandler
Indicates that one entity is responsible for managing, controlling, or processing another entity.
-
C.
hasMainEventers
Indicates that certain entities are the primary or headline participants in a particular event.
-
D.
hasListeningEvent
Indicates that an entity participates in or is associated with an event in which listening or audio consumption occurs.
-
E.
hasEventRecorder
Indicates that an entity is associated with or uses a specific device or system responsible for recording events or occurrences.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:36 a.m.