Triple
T25107371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilbert's first problem |
E628900
|
entity |
| Predicate | resolutionYearPartial |
P84500
|
FINISHED |
| Object | 1938 |
—
|
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: 1938 | Statement: [Hilbert's first problem, resolutionYearPartial, 1938]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolutionYearPartial Context triple: [Hilbert's first problem, resolutionYearPartial, 1938]
-
A.
rescueYear
Indicates the year in which a rescue event involving the entity took place.
-
B.
resolutionAdoptionYear
chosen
Indicates the year in which a resolution was formally adopted.
-
C.
returnYear
Indicates the year in which something is returned or given back to its original owner, place, or state.
-
D.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
E.
yearDecided
Indicates the specific calendar year in which a decision, ruling, or resolution was formally made or finalized.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46571d33881909e0dce54f0929239 |
completed | May 1, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:26 a.m.