Triple
T20352208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo B |
E496039
|
entity |
| Predicate | luminosityCharacteristic |
P12945
|
FINISHED |
| Object | low luminosity |
—
|
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: low luminosity | Statement: [Leo B, luminosityCharacteristic, low luminosity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: luminosityCharacteristic Context triple: [Leo B, luminosityCharacteristic, low luminosity]
-
A.
luminosityClass
Indicates the stellar luminosity classification that specifies a star’s intrinsic brightness and evolutionary stage.
-
B.
lightingCharacteristic
Indicates the specific qualities or properties of how something is lit, such as brightness, color, direction, or style of illumination.
-
C.
astronomicalCharacteristic
chosen
Indicates that one entity has a specific astronomical property, feature, or attribute in relation to another entity.
-
D.
luminosity_W
Indicates the luminosity of an object measured in watts, representing the total power it emits as electromagnetic radiation.
-
E.
designLuminosity
Indicates the specified luminosity level or brightness characteristics that something is designed or intended to have.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67850ace48190b19aff5780fef7e8 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.