Triple
T16657634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassiopeia |
E404771
|
entity |
| Predicate | constellationShape |
P124165
|
FINISHED |
| Object | W-shaped asterism |
—
|
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: W-shaped asterism | Statement: [Cassiopeia, constellationShape, W-shaped asterism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constellationShape Context triple: [Cassiopeia, constellationShape, W-shaped asterism]
-
A.
constellationType
Indicates that one entity is classified as a specific type or category of constellation in relation to another entity.
-
B.
constellationName
Indicates that an entity is identified by the proper name of a constellation.
-
C.
relatedConstellation
Indicates a relationship where one entity is associated with, connected to, or corresponds to a particular constellation.
-
D.
usesConstellation
Indicates that one entity makes use of, relies on, or incorporates a particular constellation in its function, representation, or operation.
-
E.
constellationFamily
Indicates that one constellation belongs to the same traditional family or grouping of constellations as another.
- 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_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. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:18 a.m.