Triple
T11466761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middlebrook 7H9 broth |
E271798
|
entity |
| Predicate | hasPHRange |
P2070
|
FINISHED |
| Object | approximately 6.6 to 7.0 |
—
|
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: approximately 6.6 to 7.0 | Statement: [Middlebrook 7H9 broth, hasPHRange, approximately 6.6 to 7.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPHRange Context triple: [Middlebrook 7H9 broth, hasPHRange, approximately 6.6 to 7.0]
-
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.
hasSalinityRange
Indicates the range of salinity values within which something (such as a substance, environment, or organism) is present, applicable, or able to function.
-
D.
hasAreaRange
Indicates that something’s area falls within a specified minimum-to-maximum range.
-
E.
hasHumidity
Indicates that one entity possesses, exhibits, or is characterized by a certain level or measure of humidity.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f5eb988190b309b8e309f6d1a5 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.