Triple
T6833446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gauss |
E157391
|
entity |
| Predicate | isCoherentInSI |
P71159
|
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: [gauss, isCoherentInSI, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoherentInSI Context triple: [gauss, isCoherentInSI, false]
-
A.
isCoherentSIUnit
chosen
Indicates that a unit is a valid, internally consistent unit within the International System of Units (SI), derived strictly from SI base units without additional numerical factors.
-
B.
SIUnit
Indicates that something is expressed or measured using a unit from the International System of Units (SI).
-
C.
isMetric
Indicates that something satisfies the properties required to be considered a metric, such as defining distances that obey non-negativity, identity, symmetry, and the triangle inequality.
-
D.
isIntegerUnitIn
Indicates that one integer-valued unit is contained within, or belongs to, a specified larger unit or unit set.
-
E.
hasSIUnitForConstant
Indicates that a given constant is associated with a specific SI (International System of Units) unit used to express its value.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.