Triple
T5541456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sterope I |
E145298
|
entity |
| Predicate | hasLuminosity |
P5343
|
FINISHED |
| Object | about 100 times solar 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: about 100 times solar luminosity | Statement: [Sterope I, hasLuminosity, about 100 times solar luminosity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLuminosity Context triple: [Sterope I, hasLuminosity, about 100 times solar luminosity]
-
A.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
B.
designLuminosity
chosen
Indicates the specified luminosity level or brightness characteristics that something is designed or intended to have.
-
C.
apparentBrightness
Indicates how bright one object appears from the perspective or location of another, regardless of its actual intrinsic luminosity.
-
D.
hasLuster
Indicates that one entity possesses a shiny, glossy, or reflective surface quality.
-
E.
surfaceBrightnessClass
Indicates the qualitative classification of how bright an extended object (such as a galaxy) appears per unit area 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fc66cc08190b9b2a62098ecbdb1 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:35 p.m.