Triple
T22412701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta Persei |
E554031
|
entity |
| Predicate | hasMassOfTertiary |
P148066
|
FINISHED |
| Object | about 1.7 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 1.7 solar masses | Statement: [Beta Persei, hasMassOfTertiary, about 1.7 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMassOfTertiary Context triple: [Beta Persei, hasMassOfTertiary, about 1.7 solar masses]
-
A.
hasTertiaryComponent
Indicates that an entity includes or is associated with a third-level (tertiary) component within a hierarchical structure or system.
-
B.
hasMassSecondary
Indicates that an entity possesses or is associated with the mass value of a secondary object or component in a system.
-
C.
hasMassScale
Indicates that an entity is associated with a particular mass measurement scale or system used to quantify its mass.
-
D.
hasMassTerm
Indicates that one entity is classified as a mass (uncountable) term associated with another entity.
-
E.
hasMasses
Indicates that one entity possesses or is associated with one or more masses (quantities of matter).
- 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1594496348190ba25dc0193d092f2 |
completed | April 29, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:46 p.m.