Triple
T21335574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix |
E526035
|
entity |
| Predicate | hasFlamsteedStars |
P139708
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Phoenix, hasFlamsteedStars, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlamsteedStars Context triple: [Phoenix, hasFlamsteedStars, 10]
-
A.
hasNumberOfBayerFlamsteedStars
chosen
Indicates the quantity of stars in a constellation that have either Bayer or Flamsteed designations.
-
B.
flamsteedDesignation
Indicates the Flamsteed catalog number assigned to a star within its constellation, expressing that specific designation relationship.
-
C.
hasBrightStarDesignation
Indicates that an entity is assigned a specific identifier in the Bright Star Catalogue.
-
D.
hasCaldwellNumber
Indicates that an astronomical object is associated with a specific entry in the Caldwell catalog, identified by its Caldwell number.
-
E.
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.
- 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e898d6fcbc8190b83d9cfc9b4ca123 |
completed | April 22, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:43 p.m.