Triple
T29968952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilbert’s sixteenth problem |
E761264
|
entity |
| Predicate | hasHilbertProblemNumber |
P73749
|
FINISHED |
| Object | XVI |
—
|
NE NERFINISHED |
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: XVI | Statement: [Hilbert’s sixteenth problem, hasHilbertProblemNumber, XVI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHilbertProblemNumber Context triple: [Hilbert’s sixteenth problem, hasHilbertProblemNumber, XVI]
-
A.
positionInHilbertProblems
chosen
Indicates the specific numbered place that a given problem occupies within the list of Hilbert's problems.
-
B.
hasCanonicalProblem
Indicates that an entity is associated with, or exemplifies, a standard or canonical problem instance used to represent its core issue or challenge.
-
C.
hasHilbertSpace
Indicates that an entity is associated with, defined on, or characterized by a particular Hilbert space in which its states or operations are represented.
-
D.
hasIssueNumbering
Indicates that an item, such as a publication or series, is assigned a specific issue number or follows a defined issue numbering scheme.
-
E.
hasHIndex
Indicates that an entity (typically a researcher) has a specified h-index value representing their combined publication productivity and citation impact.
- 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_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 29, 2026, 6:31 p.m.