Triple
T23244493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 畢宿五 |
E581546
|
entity |
| Predicate | 變星類型 |
P29860
|
FINISHED |
| Object | 疑似不規則變星 |
—
|
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: 疑似不規則變星 | Statement: [畢宿五, 變星類型, 疑似不規則變星]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 變星類型 Context triple: [畢宿五, 變星類型, 疑似不規則變星]
-
A.
isVariableStar
Indicates that an astronomical object exhibits intrinsic brightness variations over time, classifying it as a variable star.
-
B.
notableVariableStar
Indicates that the subject is a variable star recognized as particularly significant or noteworthy in some context (e.g., scientifically, historically, or observationally).
-
C.
variableStarType
chosen
Indicates the specific classification of variability that characterizes a variable star’s changing brightness.
-
D.
isSuspectedVariableStar
Indicates that an astronomical object is believed, based on preliminary or incomplete evidence, to exhibit variability in its brightness over time but has not yet been confirmed as a variable star.
-
E.
numberOfVariableStars
Indicates the count of variable stars associated with or present in a given context or entity.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193ee37c8819091f799506fa532da |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.