Triple
T25938693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HR 509 |
E653629
|
entity |
| Predicate | hasLowStellarActivity |
P131242
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [HR 509, hasLowStellarActivity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowStellarActivity Context triple: [HR 509, hasLowStellarActivity, true]
-
A.
hasLowLuminosity
Indicates that an entity emits relatively little light or energy compared to a typical or reference level.
-
B.
hasLowStarFormation
Indicates that the entity exhibits a relatively low rate of forming new stars compared to typical astrophysical systems.
-
C.
hasStellarActivity
chosen
Indicates that an astronomical object exhibits measurable activity or variability originating from its star, such as flares, spots, or magnetic phenomena.
-
D.
hasCentralStar
Indicates that an astronomical system or structure possesses a primary star located at its center.
-
E.
hasCentralStarVisibility
Indicates that the central star of an object or system is visible from a given viewpoint or under specified observational conditions.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 22, 2026, 8:40 a.m.