Triple
T7422429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky bluegrass |
E171281
|
entity |
| Predicate | optimalpHRange |
P13474
|
FINISHED |
| Object | slightly acidic to neutral |
—
|
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: slightly acidic to neutral | Statement: [Kentucky bluegrass, optimalpHRange, slightly acidic to neutral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: optimalpHRange Context triple: [Kentucky bluegrass, optimalpHRange, slightly acidic to neutral]
-
A.
acidityLevel
Indicates the degree or intensity of acidity associated with an entity, typically measured by pH or a comparable scale.
-
B.
hasSalinityRange
Indicates the range of salinity values within which something (such as a substance, environment, or organism) is present, applicable, or able to function.
-
C.
typicalRange
chosen
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
D.
predominantOxidationStateInSolution
Indicates the oxidation state that a chemical species most commonly or primarily adopts when present in a given solution.
-
E.
preferredHumidity
Indicates the level or range of humidity that is most suitable or favored by a given entity.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2ed29ec8190804564185fe20797 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.