Triple
T22737488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrhenius acid |
E562313
|
entity |
| Predicate | applicableMedium |
P149528
|
FINISHED |
| Object | aqueous solution |
—
|
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: aqueous solution | Statement: [Arrhenius acid, applicableMedium, aqueous solution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicableMedium Context triple: [Arrhenius acid, applicableMedium, aqueous solution]
-
A.
applicationMedium
Indicates the medium or channel through which an application is submitted or communicated (e.g., online, paper, email).
-
B.
canonicalMedium
Indicates the primary or standard medium through which something is most authoritatively or typically expressed, distributed, or experienced.
-
C.
referenceMedium
Indicates that one entity serves as the medium, channel, or format through which another entity is referenced, accessed, or communicated.
-
D.
subjectMedium
Indicates the medium or channel through which the subject is expressed, communicated, or realized.
-
E.
targetMedium
Indicates the medium or channel through which an action, message, or effect is directed or intended to be delivered.
- 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.