Triple
T9175114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thermoproteus tenax |
E220179
|
entity |
| Predicate | optimalpH |
P2070
|
FINISHED |
| Object | around pH 5–6 |
—
|
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: around pH 5–6 | Statement: [Thermoproteus tenax, optimalpH, around pH 5–6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: optimalpH Context triple: [Thermoproteus tenax, optimalpH, around pH 5–6]
-
A.
waterPH
Indicates the acidity or alkalinity level (pH value) of a given body or sample of water.
-
B.
acidityLevel
chosen
Indicates the degree or intensity of acidity associated with an entity, typically measured by pH or a comparable scale.
-
C.
predominantOxidationStateInSolution
Indicates the oxidation state that a chemical species most commonly or primarily adopts when present in a given solution.
-
D.
hasMaximumEfficiencyAt
Indicates that an entity reaches or exhibits its highest possible efficiency under a specified condition, context, or parameter value.
-
E.
isHydrophilic
Indicates that something has an affinity for water, tending to interact with or dissolve in it rather than repel it.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa2f9708190a955bf28a4f04004 |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.