Triple
T23244513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 畢宿五 |
E581546
|
entity |
| Predicate | 銀河座標 |
P22651
|
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.
hasGalacticCoordinateSystem
Indicates that something is associated with or defined within a particular galactic coordinate system.
-
B.
positionRelativeToGalacticCenter
chosen
Indicates the spatial location of an entity expressed in relation to the center of its galaxy.
-
C.
galacticCenterConstellation
Indicates the constellation in which the center of a given galaxy is located.
-
D.
locatedInMilkyWayArm
Indicates that one entity is situated within a specific spiral arm of the Milky Way galaxy in which the other entity (the arm) is defined.
-
E.
astronomicalSystem
Indicates a relationship in which multiple astronomical objects are organized into a coherent physical or dynamical system (such as a planetary system, star system, or galaxy).
- 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.