Triple
T33435411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intersection Observer API |
E856227
|
entity |
| Predicate | callbackReceives |
P4382
|
FINISHED |
| Object | Array of IntersectionObserverEntry objects |
—
|
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: Array of IntersectionObserverEntry objects | Statement: [Intersection Observer API, callbackReceives, Array of IntersectionObserverEntry objects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callbackReceives Context triple: [Intersection Observer API, callbackReceives, Array of IntersectionObserverEntry objects]
-
A.
callbackType
Indicates the specific kind or category of callback event or function associated with an entity or interaction.
-
B.
receives
chosen
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
C.
receiverAction
Indicates that the receiver of something performs or is associated with a specific action in the context of that transfer or interaction.
-
D.
calledBackBy
Indicates that one entity returns a previous call or contact initiated by another entity.
-
E.
signalReception
Indicates the reception or detection of a transmitted signal by a receiving entity.
- 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_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:36 a.m.