Triple
T29389232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PrintDocumentAdapter |
E745331
|
entity |
| Predicate | hasCallbackMethod |
P90883
|
FINISHED |
| Object | onLayout |
—
|
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: onLayout | Statement: [PrintDocumentAdapter, hasCallbackMethod, onLayout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCallbackMethod Context triple: [PrintDocumentAdapter, hasCallbackMethod, onLayout]
-
A.
hasWorkingMethod
Indicates that one entity possesses or employs a functional method, procedure, or technique to achieve a particular task or outcome.
-
B.
hasClassMethod
chosen
Indicates that a class defines or contains a specific method as part of its behavior or interface.
-
C.
hasMethodType
Indicates that an entity is associated with, or characterized by, a specific type or category of method used or applied in its context.
-
D.
hasHook
Indicates that one entity possesses, is equipped with, or features a hook in relation to another entity or context.
-
E.
hasMethodSignature
Indicates that a method or function is associated with a specific formal signature, including its name, parameters, and return type.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 28, 2026, 2:41 p.m.