Triple
T32315063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Ultra Deep Field |
E825607
|
entity |
| Predicate | fieldSelectionCriterion |
P136
|
FINISHED |
| Object | low foreground dust extinction |
—
|
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: low foreground dust extinction | Statement: [Hubble Ultra Deep Field, fieldSelectionCriterion, low foreground dust extinction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldSelectionCriterion Context triple: [Hubble Ultra Deep Field, fieldSelectionCriterion, low foreground dust extinction]
-
A.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
valueCriterion
Indicates that something is evaluated or selected based on a specified standard, rule, or measure of value.
-
C.
fieldRestriction
Indicates that access to or use of a particular field, area, or domain is limited or constrained by specified rules or conditions.
-
D.
listingCriterion
Indicates the rule or standard used to determine how items are selected, ordered, or displayed in a listing.
-
E.
selectionCharacteristic
Indicates a distinguishing feature or criterion used to choose or differentiate one entity from others.
- 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_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 12:46 a.m.