Triple
T32315042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Ultra Deep Field |
E825607
|
entity |
| Predicate | angularArea |
P175
|
FINISHED |
| Object | about 11 square arcminutes |
—
|
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 11 square arcminutes | Statement: [Hubble Ultra Deep Field, angularArea, about 11 square arcminutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angularArea Context triple: [Hubble Ultra Deep Field, angularArea, about 11 square arcminutes]
-
A.
areaApprox
Indicates that one entity’s area is approximately equal to the area of another entity.
-
B.
ringArea
Indicates the area of a ring-shaped region, typically defined by the space between two concentric boundaries.
-
C.
area
chosen
Indicates that one entity has a measured two-dimensional extent or surface size quantified by another entity.
-
D.
coreAreaOf
Indicates that one entity is the central, primary, or most important area or domain of focus for another entity.
-
E.
areaBControl
Indicates that one entity has control or authority over a specific region or area labeled as B.
- 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_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:46 a.m.