Triple
T20576578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delle Caustiche |
E505232
|
entity |
| Predicate | skyRegionType |
P9997
|
FINISHED |
| Object | Milky Way star field |
—
|
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: Milky Way star field | Statement: [Delle Caustiche, skyRegionType, Milky Way star field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skyRegionType Context triple: [Delle Caustiche, skyRegionType, Milky Way star field]
-
A.
locatedInSkyRegion
chosen
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
B.
solarSystemRegion
Indicates that one entity is a region or area located within the solar system that is associated with or contains the other entity.
-
C.
cosmicLocationType
Indicates the specific kind of spatial or cosmic setting in which an entity or event is situated (e.g., galaxy, nebula, star system).
-
D.
planetRegion
Indicates that a specified region or area is located on or associated with a particular planet.
-
E.
skyHemisphere
Indicates the celestial hemisphere (e.g., northern or southern part of the sky) in which an astronomical object or event is located or observed.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a90af3608190955d2c7950726178 |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.