Triple
T32315056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Ultra Deep Field |
E825607
|
entity |
| Predicate | lightTravelTimeRange |
P29496
|
FINISHED |
| Object | up to about 13 billion 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: up to about 13 billion years | Statement: [Hubble Ultra Deep Field, lightTravelTimeRange, up to about 13 billion years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightTravelTimeRange Context triple: [Hubble Ultra Deep Field, lightTravelTimeRange, up to about 13 billion years]
-
A.
isTimeLightTravels
chosen
Indicates the duration required for light to travel between specified points or over a specified distance.
-
B.
travelTimeThroughWormholeTo
Indicates the duration required for an entity to traverse a wormhole and reach a specified destination.
-
C.
lightingTime
Indicates the time at which a lighting event or illumination occurs or is scheduled.
-
D.
lightRange
Indicates the distance or area over which a light source effectively emits or illuminates.
-
E.
distanceInLightYears
Indicates the spatial separation between two entities measured in units of light-years.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bdba43648190900f1020d6f7861d |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:46 a.m.