Triple
T33434341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Custom Elements |
E856206
|
entity |
| Predicate | hasLifecycleCallback |
P24936
|
FINISHED |
| Object | connectedCallback |
—
|
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: connectedCallback | Statement: [Custom Elements, hasLifecycleCallback, connectedCallback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLifecycleCallback Context triple: [Custom Elements, hasLifecycleCallback, connectedCallback]
-
A.
hasLifecycleFocus
Indicates that something is concerned with or emphasizes a particular stage or aspect of a lifecycle.
-
B.
supportsLifecyclePhase
Indicates that one entity provides the necessary capabilities, conditions, or compatibility for another entity to function or be applicable during a specific phase of its lifecycle.
-
C.
hasHook
chosen
Indicates that one entity possesses, is equipped with, or features a hook in relation to another entity or context.
-
D.
designedForLifecycle
Indicates that something has been intentionally created or configured to support, align with, or optimize a particular lifecycle or set of lifecycle stages.
-
E.
lifecycleBehavior
Indicates how an entity behaves, changes, or is managed over the course of its existence or lifecycle.
- 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_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 1, 2026, 1:36 a.m.