Triple
T7199567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabine reverberation formula |
E168704
|
entity |
| Predicate | hasUnitConstant |
P75769
|
FINISHED |
| Object | 0.161 for SI 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: 0.161 for SI units | Statement: [Sabine reverberation formula, hasUnitConstant, 0.161 for SI units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnitConstant Context triple: [Sabine reverberation formula, hasUnitConstant, 0.161 for SI units]
-
A.
hasSIUnitForConstant
Indicates that a given constant is associated with a specific SI (International System of Units) unit used to express its value.
-
B.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
C.
hasDerivedUnit
Indicates that one unit is derived from another unit through a defined combination of base units or mathematical operations.
-
D.
isBaseUnitOf
Indicates that one unit serves as the fundamental reference unit from which another unit in the same measurement system is defined or derived.
-
E.
isBaseUnit
Indicates that the referenced unit is a fundamental measurement unit in a system, not derived from other units.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e92b8bc08190bfcdd34ce42e3448 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e8fd9b848190b2b1beea5698422b |
completed | March 27, 2026, 8:30 p.m. |
Created at: March 27, 2026, 2:52 p.m.