Triple
T29968977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilbert’s nineteenth problem |
E761265
|
entity |
| Predicate | solutionDateApprox |
P877
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Hilbert’s nineteenth problem, solutionDateApprox, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solutionDateApprox Context triple: [Hilbert’s nineteenth problem, solutionDateApprox, 1950s]
-
A.
openingDateApproximate
Indicates that the date when something was opened or began is not known exactly and is only an approximate value.
-
B.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
recoveryDate
Indicates the date on which a recovery process or restoration of a prior state is completed or officially recorded.
-
D.
repairDate
Indicates the date on which a repair action was performed or is scheduled to be performed on an entity.
-
E.
approvalDate
Indicates the date on which an action, request, or item was formally approved.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6786c984c8190b7668a6232901b30 |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:31 p.m.