Triple
T18443942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TY Coronae Australis |
E450605
|
entity |
| Predicate | hasVariableAccretion |
P60002
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [TY Coronae Australis, hasVariableAccretion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariableAccretion Context triple: [TY Coronae Australis, hasVariableAccretion, yes]
-
A.
hasAccretionActivity
chosen
Indicates that an object is currently undergoing or exhibiting accretion, i.e., the process of accumulating mass from surrounding material.
-
B.
hasVariability
Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
-
C.
hasVariableStarDesignation
Indicates that an entity is assigned a specific variable star designation in an astronomical naming system.
-
D.
isVariableStar
Indicates that an astronomical object exhibits intrinsic brightness variations over time, classifying it as a variable star.
-
E.
hasVariable
Indicates that one entity includes, defines, or is associated with a particular variable.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c142abc8190b4f6f938acdc413d |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.