Triple
T18552114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassiopeia |
E453402
|
entity |
| Predicate | notableAsterism |
P20372
|
FINISHED |
| Object | W-shaped pattern of five bright stars |
—
|
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 pattern of five bright stars | Statement: [Cassiopeia, notableAsterism, W-shaped pattern of five bright stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAsterism Context triple: [Cassiopeia, notableAsterism, W-shaped pattern of five bright stars]
-
A.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
B.
starKnownAs
Indicates that a particular star is referred to or identified by a specific name or designation.
-
C.
containsAsterism
chosen
Indicates that one entity includes or encompasses an asterism (a recognizable pattern or grouping of stars) within its extent or definition.
-
D.
relatedConstellation
Indicates a relationship where one entity is associated with, connected to, or corresponds to a particular constellation.
-
E.
constellationName
Indicates that an entity is identified by the proper name of a constellation.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e538019a74819099dbd255fb21fa95 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.