Triple
T8684943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universe |
E206133
|
entity |
| Predicate | hasObservableRadius |
P67815
|
FINISHED |
| Object | about 46.5 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 46.5 billion light-years | Statement: [Universe, hasObservableRadius, about 46.5 billion light-years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObservableRadius Context triple: [Universe, hasObservableRadius, about 46.5 billion light-years]
-
A.
hasCoveringRadius
Indicates the maximum distance from any point in a space to the nearest point in a given set, defining how well that set covers the space.
-
B.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
C.
hasObservationArea
Indicates that an entity possesses or includes a designated area from which observations or monitoring activities are conducted.
-
D.
hasRadiusType
Indicates that an entity has a radius characterized by a specific type or classification.
-
E.
hasOuterBoundaryRadius
chosen
Indicates that an entity has an outer boundary characterized by a specific radius measurement.
- 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.