Triple
T13002090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSSOM View Module |
E322192
|
entity |
| Predicate | definesEvent |
P93441
|
FINISHED |
| Object | resize event on Window |
—
|
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: resize event on Window | Statement: [CSSOM View Module, definesEvent, resize event on Window]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesEvent Context triple: [CSSOM View Module, definesEvent, resize event on Window]
-
A.
introducedEvent
Indicates that an entity is responsible for bringing an event into existence or initiating it for the first time.
-
B.
symbolicEvent
Indicates that an event functions primarily as a symbol or representation of something else, such as an idea, concept, or broader situation.
-
C.
eventoDesencadenante
Indicates that one event serves as the trigger or initiating cause for another event or process.
-
D.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
E.
exposesEvent
chosen
Indicates that one entity makes an event available or visible for use, handling, or observation by another entity or system.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9828748190b2ad9ea29180b7d3 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:47 p.m.