Triple
T18842345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion Bar |
E460827
|
entity |
| Predicate | astronomicalRegionType |
P103475
|
FINISHED |
| Object | bright rim |
—
|
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: bright rim | Statement: [Orion Bar, astronomicalRegionType, bright rim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: astronomicalRegionType Context triple: [Orion Bar, astronomicalRegionType, bright rim]
-
A.
astronomicalType
Indicates the classification relationship that specifies what kind of astronomical object or phenomenon something is (e.g., star, galaxy, planet).
-
B.
cosmicLocationType
chosen
Indicates the specific kind of spatial or cosmic setting in which an entity or event is situated (e.g., galaxy, nebula, star system).
-
C.
constellationType
Indicates that one entity is classified as a specific type or category of constellation in relation to another entity.
-
D.
locatedInSkyRegion
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
E.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8eb32548190b2313e877f6ff179 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.