Triple
T19685790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andromeda |
E472707
|
entity |
| Predicate | numberOfStarsInBayerFlamsteedDesignation |
P10942
|
FINISHED |
| Object | 65 |
—
|
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: 65 | Statement: [Andromeda, numberOfStarsInBayerFlamsteedDesignation, 65]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfStarsInBayerFlamsteedDesignation Context triple: [Andromeda, numberOfStarsInBayerFlamsteedDesignation, 65]
-
A.
numberOfStarsInConstellation
chosen
Indicates the numerical count of stars that belong to a given constellation.
-
B.
usesStarDesignationSystem
Indicates that one entity adopts or applies a particular star designation system to name or classify stars in relation to another entity or context.
-
C.
flamsteedDesignation
Indicates the Flamsteed catalog number assigned to a star within its constellation, expressing that specific designation relationship.
-
D.
numberOfStellationsClassified
Indicates the count of distinct stellations that have been identified and formally classified for a given object.
-
E.
hasBrightStarDesignation
Indicates that an entity is assigned a specific identifier in the Bright Star Catalogue.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641c33b94819081bdeb56910f6ff8 |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.