Triple
T22737565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrhenius base |
E562314
|
entity |
| Predicate | typicalBonding |
P149533
|
FINISHED |
| Object | ionic |
—
|
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: ionic | Statement: [Arrhenius base, typicalBonding, ionic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBonding Context triple: [Arrhenius base, typicalBonding, ionic]
-
A.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
B.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
C.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalCommitment
Indicates a standard or commonly expected level of obligation or promise that one entity holds toward another or toward performing an action.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179707fd081909aed9b2f62b9f842 |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:22 p.m.