Triple
T23687491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewis acid–base theory |
E585208
|
entity |
| Predicate | broadensConceptBeyond |
P134763
|
FINISHED |
| Object | proton transfer |
—
|
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: proton transfer | Statement: [Lewis acid–base theory, broadensConceptBeyond, proton transfer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadensConceptBeyond Context triple: [Lewis acid–base theory, broadensConceptBeyond, proton transfer]
-
A.
expandsConcept
chosen
Indicates that one concept broadens, elaborates, or adds detail to the meaning or scope of another concept.
-
B.
extendsBeyond
Indicates that one entity continues past or surpasses the spatial, temporal, or conceptual limits of another entity.
-
C.
conceptualScope
Indicates the range or domain of ideas, concepts, or topics that something (such as a work, theory, or term) is intended to cover or address.
-
D.
extendedTowards
Indicates that one entity is stretched or directed outward in the direction of another entity or location.
-
E.
generalizationTo
Indicates that one concept or entity is a more general, abstract, or encompassing version of another, capturing a broader category or superset relationship.
- 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_69f1b5bf1c10819085d48c4225cc63fc |
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.