Triple
T22412659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algol |
E554030
|
entity |
| Predicate | hasLuminosityOfSecondary |
P148062
|
FINISHED |
| Object | about 4 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 4 times solar luminosity | Statement: [Algol, hasLuminosityOfSecondary, about 4 times solar luminosity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLuminosityOfSecondary Context triple: [Algol, hasLuminosityOfSecondary, about 4 times solar luminosity]
-
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.
hasMassSecondary
Indicates that an entity possesses or is associated with the mass value of a secondary object or component in a system.
-
D.
hasSecondaryComponent
Indicates that an entity includes or is associated with an additional, subordinate component beyond its primary one.
-
E.
hasLumen
Indicates that one entity possesses or is characterized by a specific luminous intensity or light output measured in lumens.
- 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.