Triple
T22621130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Monocerotis |
E558281
|
entity |
| Predicate | coreFusionType |
P18973
|
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: [Alpha Monocerotis, coreFusionType, helium-core burning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreFusionType Context triple: [Alpha Monocerotis, coreFusionType, helium-core burning]
-
A.
coreFusion
Indicates a relationship where two or more central or fundamental components are merged into a single unified core.
-
B.
typicalCoreType
chosen
Indicates that something is a standard or characteristic core type within a given classification or system.
-
C.
coreUnitType
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
-
D.
coreDefinition
Indicates the fundamental, central meaning or essence that defines something at its most basic level.
-
E.
fuseType
Indicates the specific kind or category of fuse associated with or used in relation to an entity.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e39959481909e0ae67379435f95 |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3 p.m.