Triple
T25433410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pólya’s conjecture |
E637315
|
entity |
| Predicate | disproofYear |
P91858
|
FINISHED |
| Object | 1958 |
—
|
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: 1958 | Statement: [Pólya’s conjecture, disproofYear, 1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disproofYear Context triple: [Pólya’s conjecture, disproofYear, 1958]
-
A.
repudiatedInYear
Indicates that the relationship or agreement was formally rejected, renounced, or disowned in the specified year.
-
B.
debunkedBy
Indicates that a claim, idea, or assertion has been shown to be false or misleading by another party through evidence or argument.
-
C.
hasCounterexampleYear
chosen
Indicates the year in which a counterexample to a claim, conjecture, or statement was found or demonstrated.
-
D.
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.
-
E.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6dc7d088190b1e4c191172ea256 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:59 p.m.