Triple
T22710327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABCL |
E561573
|
entity |
| Predicate | canCallFromLisp |
P19950
|
FINISHED |
| Object | Java 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: Java methods | Statement: [ABCL, canCallFromLisp, Java methods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCallFromLisp Context triple: [ABCL, canCallFromLisp, Java methods]
-
A.
canBeCalledInto
Indicates that one entity has the authority or ability to summon, request the presence of, or formally convene another entity.
-
B.
canBeCalled
Indicates that one entity is able or permitted to be addressed, referred to, or named by another entity in a particular way.
-
C.
canBeCalledTo
Indicates that one entity is able or permitted to initiate a call or summon another entity.
-
D.
canBeInvokedFrom
chosen
Indicates that one entity (such as a function, method, or component) is able to be called or triggered directly from another specified context or entity.
-
E.
canBeInvokedBy
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17907d7288190bb53f76974f95cef |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:17 p.m.