Triple
T23953809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | positive mass theorem |
E603722
|
entity |
| Predicate | firstCompleteProofYear |
P27180
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [positive mass theorem, firstCompleteProofYear, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCompleteProofYear Context triple: [positive mass theorem, firstCompleteProofYear, 1979]
-
A.
hasFirstProofYear
chosen
Indicates the year in which something was first proven or formally demonstrated to be true.
-
B.
wasFirstProvedBy
Indicates that a particular statement, theorem, or result was originally and for the first time demonstrated or established as true by a specified agent.
-
C.
firstCompleterYear
Indicates the calendar or academic year in which an entity first completed a specified program, requirement, or activity.
-
D.
firstAchievedInYear
Indicates the year in which something was first accomplished, attained, or realized.
-
E.
firstSolutionYear
Indicates the year in which the first solution to a given problem, task, or case was achieved or recorded.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d558748190a51b5732a3e6713c |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.