Triple

T33435410
Position Surface form Disambiguated ID Type / Status
Subject Intersection Observer API E856227 entity
Predicate callbackInvokedWhen P168702 FINISHED
Object Intersection of target and root crosses a threshold 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: Intersection of target and root crosses a threshold | Statement: [Intersection Observer API, callbackInvokedWhen, Intersection of target and root crosses a threshold]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: callbackInvokedWhen
Context triple: [Intersection Observer API, callbackInvokedWhen, Intersection of target and root crosses a threshold]
  • A. callbackType
    Indicates the specific kind or category of callback event or function associated with an entity or interaction.
  • B. calledBackBy
    Indicates that one entity returns a previous call or contact initiated by another entity.
  • C. calledEvent
    Indicates that an entity initiated or made a phone call to another entity during a specific event or time.
  • D. calledAs
    Indicates that one entity is referred to, named, or addressed by another specific name or label.
  • E. triggerMethod chosen
    Indicates the method, mechanism, or procedure by which a particular event, action, or process is initiated or triggered.
  • 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_69f6e4857f3c819086399a37e954c6e9 completed May 3, 2026, 6 a.m.
PD Predicate disambiguation batch_69f6e3da41948190a4cfe866ce184f73 completed May 3, 2026, 5:57 a.m.
Created at: May 1, 2026, 1:36 a.m.