Triple
T33435654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Device Orientation Events |
E856232
|
entity |
| Predicate | hasEventTarget |
P83867
|
FINISHED |
| Object | window object |
—
|
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: window object | Statement: [Device Orientation Events, hasEventTarget, window object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventTarget Context triple: [Device Orientation Events, hasEventTarget, window object]
-
A.
eventTarget
chosen
Indicates that an event is directed toward, affects, or is intended for a particular target entity.
-
B.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
C.
hasPrimaryEvent
Indicates that an entity is associated with or linked to its main or most significant event.
-
D.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
E.
hasDeterminingEvent
Indicates that one event or occurrence serves as the decisive cause, condition, or basis that determines another situation, outcome, or state.
- 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_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:36 a.m.