Triple
T21884531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 36486 |
E540370
|
entity |
| Predicate | hasMassSecondary |
P146046
|
FINISHED |
| Object | about 8 solar masses |
—
|
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 8 solar masses | Statement: [HD 36486, hasMassSecondary, about 8 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMassSecondary Context triple: [HD 36486, hasMassSecondary, about 8 solar masses]
-
A.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
B.
hasSecondarySee
Indicates that an entity has an additional, secondary “see also” reference or cross-link to another related entity.
-
C.
hasSecondaryBase
Indicates that an entity possesses or is associated with a secondary or additional base, distinct from its primary base.
-
D.
hasSecondarySubject
Indicates that an entity is associated with an additional, non-primary subject in a given context or relationship.
-
E.
hasSecondaryMaxim
Indicates that an entity is associated with an additional, subordinate guiding principle or rule beyond its primary maxim.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118eabb008190ab6f1364ef4e6feb |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 7:05 p.m.