Triple
T19590355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benedict's reagent |
E470213
|
entity |
| Predicate | advantageOverFehling |
P136379
|
FINISHED |
| Object | greater stability on storage |
—
|
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: greater stability on storage | Statement: [Benedict's reagent, advantageOverFehling, greater stability on storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advantageOverFehling Context triple: [Benedict's reagent, advantageOverFehling, greater stability on storage]
-
A.
isSweeterThan
Indicates that one entity has a higher level of sweetness in taste compared to another entity.
-
B.
sweetenerType
Indicates the specific kind or category of sweetener associated with or used in relation to an entity.
-
C.
allowsTastingOf
Indicates that one entity permits another entity to sample or try the taste of something.
-
D.
sweetening
Indicates the action or process of making something taste sweeter, often by adding a sweet substance.
-
E.
tanninLevel
Indicates the degree or intensity of tannins present in or associated with something, typically a beverage like wine or tea.
- F. None of above. chosen
Provenance (4 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640552db48190b34555e4b72a75c4 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:43 p.m.