Triple
T22636693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sh 2-276 |
E558699
|
entity |
| Predicate | angularPositionRelativeTo |
P149022
|
FINISHED |
| Object | surrounds Orion Nebula region |
—
|
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: surrounds Orion Nebula region | Statement: [Sh 2-276, angularPositionRelativeTo, surrounds Orion Nebula region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angularPositionRelativeTo Context triple: [Sh 2-276, angularPositionRelativeTo, surrounds Orion Nebula region]
-
A.
angularPosition
Indicates the rotational orientation or angle of one entity relative to a reference direction or frame.
-
B.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
C.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
D.
locationRelativeToBorder
Indicates the position or placement of something in relation to a specified border or boundary.
-
E.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1700e11688190b33e280a653db141 |
completed | April 29, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:03 p.m.