Triple
T19395758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Scuti |
E485183
|
entity |
| Predicate | celestialSphereLocation |
P9997
|
FINISHED |
| Object | southern celestial hemisphere |
—
|
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: southern celestial hemisphere | Statement: [Alpha Scuti, celestialSphereLocation, southern celestial hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celestialSphereLocation Context triple: [Alpha Scuti, celestialSphereLocation, southern celestial hemisphere]
-
A.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
B.
positionInConstellation
Indicates the specific location or role an object occupies within the boundaries or structure of a given constellation.
-
C.
locationOnTelescope
Indicates that one entity is positioned at or attached to a specific part or place on a telescope.
-
D.
celestialRepresentation
Indicates that one entity serves as a symbolic or visual depiction of another entity in a celestial or astronomical context.
-
E.
locatedInSkyRegion
chosen
Indicates that an entity is situated within or associated with a specific region or area of the sky.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b4875ac8190a9c184c075b5db16 |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.