Triple
T31019067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkeley Pit |
E790403
|
entity |
| Predicate | waterpH |
P83946
|
FINISHED |
| Object | highly acidic |
—
|
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: highly acidic | Statement: [Berkeley Pit, waterpH, highly acidic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterpH Context triple: [Berkeley Pit, waterpH, highly acidic]
-
A.
waterPH
chosen
Indicates the acidity or alkalinity level (pH value) of a given body or sample of water.
-
B.
waterCondition
Indicates the state or quality of water affecting an entity, such as its cleanliness, safety, or suitability for a particular use.
-
C.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
D.
waterTension
Indicates the relationship in which a liquid exhibits surface tension, resisting external force at its interface due to cohesive molecular forces.
-
E.
waterFunction
Indicates that one entity serves a particular role, purpose, or function in relation to water (e.g., how it uses, manages, affects, or interacts with water).
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 29, 2026, 8:58 p.m.