Triple
T22737563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrhenius base |
E562314
|
entity |
| Predicate | hasChargeBeforeDissociation |
P8394
|
FINISHED |
| Object | often neutral |
—
|
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: often neutral | Statement: [Arrhenius base, hasChargeBeforeDissociation, often neutral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChargeBeforeDissociation Context triple: [Arrhenius base, hasChargeBeforeDissociation, often neutral]
-
A.
hasCharge
chosen
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
B.
hasChargeConjugation
Indicates that one entity is the charge-conjugated counterpart (particle vs. antiparticle form) of another entity.
-
C.
hasChargePosition
Indicates that one entity occupies or is assigned to a particular official role, office, or position of responsibility within another entity.
-
D.
containsCharge
Indicates that one entity includes, holds, or encompasses a specific charge associated with it.
-
E.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
- 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_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. |
Created at: April 17, 2026, 3:22 p.m.