Triple
T18257592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble constant |
E437255
|
entity |
| Predicate | hasTypicalUnit |
P41758
|
FINISHED |
| Object | kilometers per second per megaparsec |
—
|
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: kilometers per second per megaparsec | Statement: [Hubble constant, hasTypicalUnit, kilometers per second per megaparsec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalUnit Context triple: [Hubble constant, hasTypicalUnit, kilometers per second per megaparsec]
-
A.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
B.
typicalUnitType
chosen
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
-
C.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
D.
typicalSupportedUnitType
Indicates the kind or category of unit that an entity is normally designed or expected to support.
-
E.
hasBasicUnit
Indicates that one entity is composed of, defined by, or fundamentally characterized through another entity that serves as its basic or minimal unit.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd86e21081909c049082949b95c6 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.