Triple
T8684944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universe |
E206133
|
entity |
| Predicate | hasObservableDiameter |
P7302
|
FINISHED |
| Object | about 93 billion light-years |
—
|
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 93 billion light-years | Statement: [Universe, hasObservableDiameter, about 93 billion light-years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObservableDiameter Context triple: [Universe, hasObservableDiameter, about 93 billion light-years]
-
A.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
B.
meanDiameter_km
Indicates the average diameter of an object or region measured in kilometers.
-
C.
hasPolarDiameter_km
Indicates the length of an object's diameter measured from pole to pole, expressed in kilometers.
-
D.
hasEquatorialDiameter_km
Indicates the measurement, in kilometers, of an object's diameter across its equator.
-
E.
approximateDiameter
chosen
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4aeae740819099093906ccc5f640 |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.