Triple
T32212875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3D-HST survey |
E822853
|
entity |
| Predicate | usesPhotometryFrom |
P182860
|
FINISHED |
| Object | CANDELS survey |
—
|
NE NERFINISHED |
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: CANDELS survey | Statement: [3D-HST survey, usesPhotometryFrom, CANDELS survey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPhotometryFrom Context triple: [3D-HST survey, usesPhotometryFrom, CANDELS survey]
-
A.
hasPhotometry
Indicates that an entity possesses or is associated with photometric data or measurements.
-
B.
photometricSystem
Indicates the photometric measurement system or filter set used when observing or recording a quantity.
-
C.
usesPhotographyFrom
Indicates that one entity employs or incorporates photographic material originating from another entity.
-
D.
hasCombinedApparentMagnitude
Indicates that a group of astronomical objects, when considered together, have a specific total apparent brightness as seen by an observer.
-
E.
requiresTelescopeAperture
Indicates that performing the specified observation or task depends on using a telescope with at least a certain aperture size.
- F. None of above. chosen
Provenance (4 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 1, 2026, 12:37 a.m.