Triple
T35140792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNotifyEvent |
E1014696
|
entity |
| Predicate | isMethodPointerTo |
P21339
|
FINISHED |
| Object | object method |
—
|
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: object method | Statement: [TNotifyEvent, isMethodPointerTo, object method]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMethodPointerTo Context triple: [TNotifyEvent, isMethodPointerTo, object method]
-
A.
positionOnMethod
Indicates the specific location or placement of something within the structure or sequence of a method.
-
B.
implementsMethod
Indicates that one entity provides a concrete implementation of a specified method defined or required elsewhere.
-
C.
isUsedToInvoke
Indicates that one entity serves as a means or mechanism to trigger, call, or activate another entity or process.
-
D.
hasStackPointer
Indicates that an entity maintains or uses a specific stack pointer reference within a stack-based memory or execution context.
-
E.
hasMethodType
chosen
Indicates that an entity is associated with, or characterized by, a specific type or category of method used or applied in its context.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78caa838c8190a7ebc02fe81ecb1c |
completed | May 3, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.