Triple
T28531230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milk |
E722046
|
entity |
| Predicate | typicalpH |
P2070
|
FINISHED |
| Object | 6.5–6.7 |
—
|
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: 6.5–6.7 | Statement: [Milk, typicalpH, 6.5–6.7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalpH Context triple: [Milk, typicalpH, 6.5–6.7]
-
A.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
B.
acidityLevel
chosen
Indicates the degree or intensity of acidity associated with an entity, typically measured by pH or a comparable scale.
-
C.
typicalPhenolLevel
Indicates that the phenol concentration or level falls within a normal or characteristic range for the given context.
-
D.
typicalAlpha
Indicates that an entity exhibits the characteristic or behavior considered standard or representative (i.e., “typical”) for a given group, category, or context.
-
E.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00b3d2e0c88190a8bf49576e654f64 |
completed | May 10, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_6a00b376f4e48190a6676779fe02ea9f |
completed | May 10, 2026, 4:33 p.m. |
Created at: April 28, 2026, 3:28 a.m.