Triple
T18257618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble constant |
E437255
|
entity |
| Predicate | earlyEstimateWas |
P55909
|
FINISHED |
| Object | about 500 km s⁻¹ Mpc⁻¹ |
—
|
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: about 500 km s⁻¹ Mpc⁻¹ | Statement: [Hubble constant, earlyEstimateWas, about 500 km s⁻¹ Mpc⁻¹]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyEstimateWas Context triple: [Hubble constant, earlyEstimateWas, about 500 km s⁻¹ Mpc⁻¹]
-
A.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
B.
areEstimatedIn
chosen
Indicates that a value or quantity is approximated or inferred within a specified context, framework, or unit.
-
C.
estimatedUsing
Indicates that one entity’s value, state, or outcome is derived by applying an estimation method, model, or procedure based on another entity.
-
D.
earlyActivity
Indicates that an entity begins or performs a specified activity earlier than a usual, expected, or referenced time.
-
E.
earlyVersion
Indicates that one entity is an earlier or preliminary version of another entity in a version sequence.
- 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.