Triple
T9171558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilbert’s twenty-second problem |
E220091
|
entity |
| Predicate | statedInYear |
P86624
|
FINISHED |
| Object | 1900 |
—
|
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: 1900 | Statement: [Hilbert’s twenty-second problem, statedInYear, 1900]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statedInYear Context triple: [Hilbert’s twenty-second problem, statedInYear, 1900]
-
A.
declaredYear
Indicates the year in which something was formally announced, established, or proclaimed.
-
B.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
C.
describedYear
Indicates the specific year in which something is described, documented, or characterized.
-
D.
foundInYear
Indicates the specific calendar year in which something was discovered, created, established, or otherwise found.
-
E.
tookPlaceInYear
Indicates that an event or occurrence happened during a specific calendar year.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaae38ee48190bf783477bc37913d |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:22 p.m.