Triple
T22710328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABCL |
E561573
|
entity |
| Predicate | canInstantiateFromLisp |
P149411
|
FINISHED |
| Object | Java objects |
—
|
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 objects | Statement: [ABCL, canInstantiateFromLisp, Java objects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canInstantiateFromLisp Context triple: [ABCL, canInstantiateFromLisp, Java objects]
-
A.
instantiatedBy
Indicates that a specific instance or concrete realization is created, defined, or derived from a more abstract template, class, or specification.
-
B.
canBeConstructedWith
Indicates that one entity can be formed, built, or assembled using another entity as material, components, or means.
-
C.
hasConstructor
Indicates that an entity defines or is associated with a specific constructor used to create or initialize instances of it.
-
D.
canBeImplementedWith
Indicates that one entity is capable of being realized, executed, or fulfilled through the use or application of another entity.
-
E.
constructedWithFunction
Indicates that something is created or built using a specific function as the primary means or method of construction.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:17 p.m.