Triple
T23687715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewis base |
E585212
|
entity |
| Predicate | canBeClassifiedBy |
P25488
|
FINISHED |
| Object | hard–soft acid–base theory |
—
|
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: hard–soft acid–base theory | Statement: [Lewis base, canBeClassifiedBy, hard–soft acid–base theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeClassifiedBy Context triple: [Lewis base, canBeClassifiedBy, hard–soft acid–base theory]
-
A.
areClassifiedBy
chosen
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
B.
usesClassificationCriteria
Indicates that one entity applies specific classification criteria to categorize, organize, or evaluate another entity.
-
C.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
D.
supportsClassification
Indicates that one entity provides the capability or functionality needed for another entity to perform or maintain a specific classification.
-
E.
usedToClassify
Indicates that one entity serves as a criterion or basis for categorizing or grouping 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5bfe15c8190af2b4c451bccae16 |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.