Triple
T11219218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | h-cobordism theorem |
E265515
|
entity |
| Predicate | provedInYear |
P27180
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [h-cobordism theorem, provedInYear, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provedInYear Context triple: [h-cobordism theorem, provedInYear, 1961]
-
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.
statedInYear
Indicates that something was declared, expressed, or formally stated during a specific calendar year.
-
D.
proposedInYear
Indicates that something, such as a plan, idea, or piece of legislation, was formally put forward or suggested in a specific calendar year.
-
E.
introducedInPublicationYear
Indicates the year in which something (such as a concept, method, or product) was first introduced or presented in a publication.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8eb84c48190b4f3bede254afde2 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.