Triple
T15867777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leptogenesis |
E384755
|
entity |
| Predicate | conversionMechanism |
P39633
|
FINISHED |
| Object | sphaleron processes |
—
|
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: sphaleron processes | Statement: [Leptogenesis, conversionMechanism, sphaleron processes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionMechanism Context triple: [Leptogenesis, conversionMechanism, sphaleron processes]
-
A.
conversionUse
Indicates that one entity is used as a means, method, or context for converting another entity from one form, state, or representation to another.
-
B.
conversionTarget
Indicates that one entity serves as the intended outcome, goal, or result that another entity is meant to be converted or transformed into.
-
C.
conversionProcess
chosen
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
-
D.
conversionProgram
Indicates a program or process that transforms something from one form, state, or type into another.
-
E.
conversionName
Indicates that one entity is the name or label assigned to a specific conversion event or conversion process associated with another 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:50 a.m.