Triple
T6457825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 23480 |
E142036
|
entity |
| Predicate | hasDominantFusionProcess |
P21600
|
FINISHED |
| Object | hydrogen fusion in core |
—
|
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: hydrogen fusion in core | Statement: [HD 23480, hasDominantFusionProcess, hydrogen fusion in core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDominantFusionProcess Context triple: [HD 23480, hasDominantFusionProcess, hydrogen fusion in core]
-
A.
dominantFusionProcess
chosen
Indicates that one fusion process is the primary or prevailing mechanism compared to other possible fusion processes in a given context.
-
B.
hasDominantUse
Indicates that one use or function of an entity is primary or prevailing over its other possible uses.
-
C.
dominantGeneration
Indicates that one generation in a life cycle is more prominent, long-lived, or visually conspicuous than the other generation(s).
-
D.
hasDominanceSystem
Indicates that one entity maintains a structured hierarchy of power or control over others within a social or organizational system.
-
E.
dominantProcess
Indicates that one process exerts primary control or influence over another process within a given context.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069d758508190b9c7358ef84f8169 |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:48 p.m.