Triple
T28616633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PageSetupDlg |
E724286
|
entity |
| Predicate | supportsHookProcedure |
P24936
|
FINISHED |
| Object | PageSetupHookProc |
—
|
NE NERFINISHED |
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: PageSetupHookProc | Statement: [PageSetupDlg, supportsHookProcedure, PageSetupHookProc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHookProcedure Context triple: [PageSetupDlg, supportsHookProcedure, PageSetupHookProc]
-
A.
hasHook
chosen
Indicates that one entity possesses, is equipped with, or features a hook in relation to another entity or context.
-
B.
supportsAfterRequestHooks
Indicates that an entity provides or allows the execution of hooks or callbacks after a request has been processed.
-
C.
hasPopHooks
Indicates that something (such as a song or musical piece) contains catchy, memorable elements characteristic of pop music.
-
D.
hookOf
Indicates that one entity functions as a hook or hooking component that is part of, attached to, or used by another entity.
-
E.
supportsModule
Indicates that one entity provides compatibility, functionality, or resources necessary for another entity’s module to operate or be used.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a016b2629c48190befb10581560d58f |
completed | May 11, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a0167d5a2088190a68dbd2b87f73e80 |
completed | May 11, 2026, 5:23 a.m. |
Created at: April 28, 2026, 4:32 a.m.