Triple
T31220753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scoville heat units |
E796002
|
entity |
| Predicate | hasAlternativeScale |
P3868
|
FINISHED |
| Object | ASTA pungency units |
—
|
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: ASTA pungency units | Statement: [Scoville heat units, hasAlternativeScale, ASTA pungency units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeScale Context triple: [Scoville heat units, hasAlternativeScale, ASTA pungency units]
-
A.
hasAlternativeMultiplierChoice
Indicates that an entity is associated with one or more alternative options for a multiplier that can be chosen instead of a default value.
-
B.
hasAlternativeBasis
Indicates that something is supported, justified, or founded on a different underlying reason, source, or principle than the primary or original one.
-
C.
hasScales
Indicates that an entity possesses scales as a surface covering or body feature.
-
D.
hasScale
chosen
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
-
E.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 29, 2026, 9:10 p.m.