Triple
T16657633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassiopeia |
E404771
|
entity |
| Predicate | constellationLocation |
P9990
|
FINISHED |
| Object | northern sky |
—
|
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: northern sky | Statement: [Cassiopeia, constellationLocation, northern sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constellationLocation Context triple: [Cassiopeia, constellationLocation, northern sky]
-
A.
positionInConstellation
Indicates the specific location or role an object occupies within the boundaries or structure of a given constellation.
-
B.
celestialLocation
chosen
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
C.
constellationName
Indicates that an entity is identified by the proper name of a constellation.
-
D.
positionInAsterism
Indicates the specific location or role that an object occupies within a defined asterism pattern.
-
E.
eclipticConstellation
Indicates the constellation in which an object lies along the ecliptic path as seen from a given reference point.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bfbfd7c819092c92f6c8da07dbd |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.