Triple
T18772085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 24131 |
E459037
|
entity |
| Predicate | hasEnergyGeneration |
P95815
|
FINISHED |
| Object | core hydrogen fusion |
—
|
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: core hydrogen fusion | Statement: [HD 24131, hasEnergyGeneration, core hydrogen fusion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergyGeneration Context triple: [HD 24131, hasEnergyGeneration, core hydrogen fusion]
-
A.
energyGenerationMechanism
chosen
Indicates the method or process by which energy is produced or generated by an entity.
-
B.
hasEnergyResource
Indicates that an entity possesses, controls, or is associated with a source of usable energy.
-
C.
includesPowerGeneration
Indicates that an entity encompasses or involves facilities, systems, or activities related to generating electrical or other forms of power.
-
D.
isMajorSourceOfElectricityFor
Indicates that one entity provides the primary or dominant share of electrical power used by another entity.
-
E.
electricPowerOutput
Indicates the amount of electrical power produced or delivered by 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.