Triple
T6175158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asellus Australis |
E137798
|
entity |
| Predicate | coreFusion |
P69240
|
FINISHED |
| Object | helium-core burning |
—
|
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: helium-core burning | Statement: [Asellus Australis, coreFusion, helium-core burning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreFusion Context triple: [Asellus Australis, coreFusion, helium-core burning]
-
A.
centerCoreReusable
Indicates that the central core component of a system or structure is designed to be reused rather than discarded after a single use.
-
B.
coreModule
Indicates that something functions as a primary or foundational module within a larger system or structure.
-
C.
formerHubFor
Indicates that one entity previously served as a central or primary hub for another entity but no longer holds that role.
-
D.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
E.
coreCondition
Indicates that something serves as the primary or fundamental condition that must hold for a situation, process, or relationship to apply.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc55b5c819084482b735771c9a8 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.