Triple
T21066581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debye unit |
E518988
|
entity |
| Predicate | hasExactValueInSI |
P74393
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Debye unit, hasExactValueInSI, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExactValueInSI Context triple: [Debye unit, hasExactValueInSI, false]
-
A.
isExactInSI
chosen
Indicates that a quantity or value is defined as an exact, non-approximate value within the International System of Units (SI).
-
B.
isCoherentWithSI
Indicates that something is consistent and compatible with the International System of Units (SI), adhering to its definitions, conventions, and relationships among units.
-
C.
hasSIUnitForConstant
Indicates that a given constant is associated with a specific SI (International System of Units) unit used to express its value.
-
D.
isNonCoherentWithSI
Indicates that something does not conform to, or is inconsistent with, the specified standard or specification interface (SI).
-
E.
valueSI
Indicates that an entity has a quantitative value expressed in SI (International System of Units) units.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb455fc81909cc63fa0e87b6a35 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:45 p.m.