Triple
T33829858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAO 164565 |
E867065
|
entity |
| Predicate | isAmStar |
P177751
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SAO 164565, isAmStar, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAmStar Context triple: [SAO 164565, isAmStar, true]
-
A.
isStandardStar
Indicates that an astronomical object is classified as a normal, main-sequence or otherwise typical star, rather than an exotic or non-standard stellar object.
-
B.
starIs
Indicates that one entity is identified or classified as a star in relation to another entity or context.
-
C.
hasStarOn
Indicates that one entity bears or displays a star symbol positioned on another entity.
-
D.
isCoolStar
Indicates that the subject is a star characterized by relatively low surface temperature compared to hotter stellar types.
-
E.
isShoulderStarOf
Indicates that one entity serves as a prominent but secondary or supporting star or featured performer alongside another, akin to a “shoulder” role next to the main star.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:46 a.m.