Triple
T23244490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 畢宿五 |
E581546
|
entity |
| Predicate | 光度 |
P119300
|
FINISHED |
| Object | 約為太陽光度的 400 倍 |
—
|
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: 約為太陽光度的 400 倍 | Statement: [畢宿五, 光度, 約為太陽光度的 400 倍]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 光度 Context triple: [畢宿五, 光度, 約為太陽光度的 400 倍]
-
A.
rayBrightness
Indicates the intensity or luminance level associated with a specific ray.
-
B.
intrinsicBrightness
chosen
Indicates the inherent level of light or luminosity an entity possesses, independent of external factors or observation conditions.
-
C.
surfaceBrightnessClass
Indicates the qualitative classification of how bright an extended object (such as a galaxy) appears per unit area on the sky.
-
D.
apparentBrightness
Indicates how bright one object appears from the perspective or location of another, regardless of its actual intrinsic luminosity.
-
E.
surfaceBrightness_V_mag_per_arcsec2
Indicates the surface brightness of an object measured in V-band magnitudes per square arcsecond, relating its emitted light to the area it covers on the sky.
- 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.