Triple
T23244499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 畢宿五 |
E581546
|
entity |
| Predicate | 佛蘭斯蒂德命名 |
P24822
|
FINISHED |
| Object | 87 Tauri |
—
|
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: 87 Tauri | Statement: [畢宿五, 佛蘭斯蒂德命名, 87 Tauri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 佛蘭斯蒂德命名 Context triple: [畢宿五, 佛蘭斯蒂德命名, 87 Tauri]
-
A.
flamsteedDesignation
chosen
Indicates the Flamsteed catalog number assigned to a star within its constellation, expressing that specific designation relationship.
-
B.
hasAstroObjectNamedAfter
Indicates that one entity has an astronomical object (such as a star, planet, asteroid, or other celestial body) named in honor of or after another entity.
-
C.
hasIAUName
Indicates that an entity is assigned an official name as recognized by the International Astronomical Union (IAU).
-
D.
hasCaldwellNumber
Indicates that an astronomical object is associated with a specific entry in the Caldwell catalog, identified by its Caldwell number.
-
E.
hasAsteroidNamedAfter
Indicates that an asteroid has been officially named in honor of a particular 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.