Triple
T19590342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benedict's reagent |
E470213
|
entity |
| Predicate | notReactiveWith |
P136376
|
FINISHED |
| Object | most non-reducing sugars |
—
|
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: most non-reducing sugars | Statement: [Benedict's reagent, notReactiveWith, most non-reducing sugars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notReactiveWith Context triple: [Benedict's reagent, notReactiveWith, most non-reducing sugars]
-
A.
nonVolatile
Indicates that the associated entity or state does not change, disappear, or lose its value when power is removed or over time.
-
B.
notTouchedBy
Indicates that one entity has not made physical contact with another entity.
-
C.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
D.
nonExclusive
Indicates that the relationship or access is shared among multiple parties and is not limited to a single, exclusive holder.
-
E.
nonTriggerFeature
Indicates that a feature or characteristic is present but does not initiate, cause, or trigger the associated event, process, or condition.
- 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.