Triple
T22279587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CfA Redshift Survey |
E550694
|
entity |
| Predicate | locationOfObservation |
P38767
|
FINISHED |
| Object | Northern Hemisphere sky |
—
|
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: Northern Hemisphere sky | Statement: [CfA Redshift Survey, locationOfObservation, Northern Hemisphere sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfObservation Context triple: [CfA Redshift Survey, locationOfObservation, Northern Hemisphere sky]
-
A.
locationOfObservance
Indicates the place where an event, ceremony, or observance occurs or is carried out.
-
B.
telescopeLocation
Indicates the physical place or site where a telescope is situated or installed.
-
C.
locationOnTelescope
Indicates that one entity is positioned at or attached to a specific part or place on a telescope.
-
D.
observatoryFor
Indicates that something serves as an observatory specifically dedicated to observing, studying, or monitoring a particular target or subject.
-
E.
observationPlatform
chosen
Indicates that one entity serves as the physical or virtual platform, site, or facility from which observations of another entity or phenomenon are made.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14eaa8cec819081c2ad031154ebe7 |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.