Triple
T34324403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 204075 |
E880826
|
entity |
| Predicate | hasLuminosityClassComponentA |
P22859
|
FINISHED |
| Object | II |
—
|
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: II | Statement: [HD 204075, hasLuminosityClassComponentA, II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLuminosityClassComponentA Context triple: [HD 204075, hasLuminosityClassComponentA, II]
-
A.
luminosityClass
chosen
Indicates the stellar luminosity classification that specifies a star’s intrinsic brightness and evolutionary stage.
-
B.
hasLuminosityOfPrimary
Indicates that one entity has the same luminosity value or luminosity classification as the primary entity in a given system or context.
-
C.
hasLCClassification
Indicates that an entity is assigned a specific Library of Congress Classification code representing its subject or shelving category.
-
D.
hasLuminosityFunction
Indicates that there is an associated luminosity function characterizing how brightness or light output is distributed for the given entity or system.
-
E.
hasLuminosityOfSecondary
Indicates that one entity has the luminosity value or brightness level associated with a secondary object in a system or relationship.
- 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.