Triple
T22053989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Orionis |
E544956
|
entity |
| Predicate | hasLuminosity_solarLuminosities |
P7281
|
FINISHED |
| Object | >100000 |
—
|
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: >100000 | Statement: [Delta Orionis, hasLuminosity_solarLuminosities, >100000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLuminosity_solarLuminosities Context triple: [Delta Orionis, hasLuminosity_solarLuminosities, >100000]
-
A.
luminosityRelativeToSun
chosen
Indicates how bright an object is compared to the Sun, expressed as a ratio of their luminosities.
-
B.
isSunLike
Indicates that one celestial object shares key physical and behavioral characteristics with the Sun, such as mass, temperature, luminosity, and spectral type.
-
C.
luminosityComparison
Indicates a relationship where the brightness or luminous intensity of one entity is compared to that of another.
-
D.
apparentMagnitude
Indicates the observed brightness of an astronomical object as seen from Earth, on a logarithmic scale where lower values correspond to brighter appearances.
-
E.
stellarMass_solarMasses
Indicates the mass of a star expressed as a multiple of the Sun’s mass.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285681848190a0bbe18d504d1f34 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.