Triple
T35086829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun |
E1012599
|
entity |
| Predicate | fusionProcess |
P65743
|
FINISHED |
| Object | proton–proton chain |
—
|
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: proton–proton chain | Statement: [Sun, fusionProcess, proton–proton chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fusionProcess Context triple: [Sun, fusionProcess, proton–proton chain]
-
A.
fusionConcept
Indicates a relationship where multiple concepts are combined or integrated into a single, unified concept.
-
B.
fusionReactionType
chosen
Indicates the specific kind or category of nuclear fusion process that relates two or more participating entities.
-
C.
mergedByProcess
Indicates that one or more entities are combined or unified as the result of a specific process.
-
D.
fusionReactionPartner
Indicates that two entities participate together as reactants in a nuclear fusion reaction.
-
E.
fusionPartner
Indicates that two entities are combined or merged to form a single, unified entity or structure.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.