Triple
T4162055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solanum lycopersicum |
E91552
|
entity |
| Predicate | pHPreference |
P2070
|
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: [Solanum lycopersicum, pHPreference, slightly acidic to neutral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pHPreference Context triple: [Solanum lycopersicum, pHPreference, slightly acidic to neutral]
-
A.
acidityLevel
chosen
Indicates the degree or intensity of acidity associated with an entity, typically measured by pH or a comparable scale.
-
B.
unitPreference
Indicates a relationship where one entity specifies or favors a particular unit of measurement or representation over others.
-
C.
preferredHumidity
Indicates the level or range of humidity that is most suitable or favored by a given entity.
-
D.
preparationPreference
Indicates how an entity prefers something to be prepared, processed, or made ready (e.g., style, method, or conditions of preparation).
-
E.
substratePreference
Indicates a relationship where an entity tends to occur on, grow in, or utilize a particular physical material or medium as its preferred substrate.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.