Triple
T15867784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leptogenesis |
E384755
|
entity |
| Predicate | oftenRealizedIn |
P120831
|
FINISHED |
| Object | type-I seesaw models |
—
|
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: type-I seesaw models | Statement: [Leptogenesis, oftenRealizedIn, type-I seesaw models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenRealizedIn Context triple: [Leptogenesis, oftenRealizedIn, type-I seesaw models]
-
A.
finalRealization
Indicates the culminating recognition or understanding that occurs at the end of a process, event, or sequence of actions.
-
B.
hasRealizationAs
Indicates that something abstract, such as a plan, design, or concept, is concretely implemented or manifested as a particular realized form.
-
C.
achievedOn
Indicates that a particular result, milestone, or state was successfully reached or completed at a specific time or date.
-
D.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
E.
oftenFormulatedOn
Indicates that something (such as a statement, plan, or decision) is frequently based on, derived from, or constructed using another thing as its foundation or starting point.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:50 a.m.