Triple
T33435454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resize Observer API |
E856228
|
entity |
| Predicate | callbackParameter |
P12016
|
FINISHED |
| Object | entries |
—
|
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: entries | Statement: [Resize Observer API, callbackParameter, entries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callbackParameter Context triple: [Resize Observer API, callbackParameter, entries]
-
A.
parameter
chosen
Indicates that one entity serves as a parameter or argument that configures, constrains, or influences the behavior or outcome of another entity or process.
-
B.
callbackType
Indicates the specific kind or category of callback event or function associated with an entity or interaction.
-
C.
genericParameter
Indicates that one entity functions as a type or template parameter that is supplied to or constrained by another entity.
-
D.
controlParameter
Indicates that one entity functions as a parameter that governs, tunes, or constrains the behavior or operation of another entity.
-
E.
parametrizes
Indicates that one entity defines or controls the variable parameters that determine the behavior, form, or configuration of another 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_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.