Triple
T29768542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V399 Carinae |
E753982
|
entity |
| Predicate | brightnessCategory |
P168681
|
FINISHED |
| Object | supergiant 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: supergiant luminosity | Statement: [V399 Carinae, brightnessCategory, supergiant luminosity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brightnessCategory Context triple: [V399 Carinae, brightnessCategory, supergiant luminosity]
-
A.
brightnessRole
Indicates a relationship where one entity serves a specific role in determining, controlling, or characterizing the brightness of another entity.
-
B.
brightnessCorrelatesWith
Indicates that changes in the brightness of one entity are systematically associated with changes in the brightness of another entity.
-
C.
brightnessRangeClass
Indicates the classification of an entity based on the range or interval of its brightness values.
-
D.
lightType
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
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. chosen
Provenance (4 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 28, 2026, 8:40 p.m.