Triple
T23244514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 畢宿五 |
E581546
|
entity |
| Predicate | 是否有行星候選 |
P27663
|
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.
hasCandidatePlanet
chosen
Indicates that an object (typically a star or system) is associated with a planet that is suspected or proposed to exist but not yet fully confirmed.
-
B.
hasCandidateExoplanets
Indicates that an astronomical object or system is associated with one or more potential exoplanets that meet specified candidacy criteria.
-
C.
hasExoplanet
Indicates that an astronomical object, typically a star, possesses one or more orbiting exoplanets.
-
D.
hasExoplanets
Indicates that the subject celestial system or star possesses one or more confirmed exoplanets in orbit around it.
-
E.
hasExoplanetsDetected
Indicates that one or more exoplanets have been observed and confirmed to exist in association with the referenced astronomical object.
- 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.