Triple
T18485200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGC 9992 |
E451669
|
entity |
| Predicate | skyArea |
P20375
|
FINISHED |
| Object | constellation region of Ursa Major |
—
|
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: constellation region of Ursa Major | Statement: [UGC 9992, skyArea, constellation region of Ursa Major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skyArea Context triple: [UGC 9992, skyArea, constellation region of Ursa Major]
-
A.
areaSquareDegrees
chosen
Indicates the extent of a region or object measured as an area on the sky in square degrees.
-
B.
skyQuality
Indicates the measured level or condition of the sky, typically in terms of clarity, brightness, or suitability for observation.
-
C.
locatedInSkyRegion
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
D.
spaceDomain
Indicates that the relationship or activity occurs within, pertains to, or is governed by the space domain (outer space and related space operations).
-
E.
observationArc
Indicates a relationship where one entity serves as an observational link or span over which another entity is monitored, tracked, or measured across a period or range.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d6502c8190af167b954bf8e989 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.