Triple
T23244510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 畢宿五 |
E581546
|
entity |
| Predicate | IAU傳統名 |
P49673
|
FINISHED |
| Object | Aldebaran |
—
|
NE NERFINISHED |
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: Aldebaran | Statement: [畢宿五, IAU傳統名, Aldebaran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IAU傳統名 Context triple: [畢宿五, IAU傳統名, Aldebaran]
-
A.
hasIAUName
chosen
Indicates that an entity is assigned an official name as recognized by the International Astronomical Union (IAU).
-
B.
belongsToIAUList
Indicates that something is included in, or officially recognized as part of, a list maintained by the International Astronomical Union (IAU).
-
C.
isNonOfficialIAU
Indicates that the entity’s designation or status is not officially recognized or approved by the International Astronomical Union (IAU).
-
D.
IAUNameApproval
Indicates that an official name for an astronomical object or feature has been formally approved by the International Astronomical Union (IAU).
-
E.
recognizedByIAUYear
Indicates the year in which an astronomical object or feature was officially recognized or approved by the International Astronomical Union (IAU).
- 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_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.