Triple
T26991364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handle-Body pattern |
E679868
|
entity |
| Predicate | typicalHandleRole |
P117349
|
FINISHED |
| Object | exposes public methods |
—
|
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: exposes public methods | Statement: [Handle-Body pattern, typicalHandleRole, exposes public methods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHandleRole Context triple: [Handle-Body pattern, typicalHandleRole, exposes public methods]
-
A.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context or system.
-
B.
typicalAdditionalRole
chosen
Indicates that an entity commonly or characteristically holds an extra role or function in addition to its primary one.
-
C.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
D.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
E.
roleAccordingTo
Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
Created at: April 27, 2026, 6:52 a.m.