Triple
T22737303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrhenius acid–base theory |
E562308
|
entity |
| Predicate | exampleBase |
P120397
|
FINISHED |
| Object | sodium hydroxide |
—
|
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: sodium hydroxide | Statement: [Arrhenius acid–base theory, exampleBase, sodium hydroxide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleBase Context triple: [Arrhenius acid–base theory, exampleBase, sodium hydroxide]
-
A.
baseExamples
chosen
Indicates that something serves as a fundamental or illustrative example for understanding or demonstrating another concept, item, or case.
-
B.
mainBase
Indicates that one entity serves as the primary or central base or headquarters for another entity.
-
C.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
D.
exampleType
Indicates that one entity serves as a representative or illustrative instance of the type or category defined by another entity.
-
E.
backendExample
Indicates that something serves as an example or illustrative instance within a backend or server-side context.
- 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.