Triple
T8850277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilbert’s seventeenth problem |
E210619
|
entity |
| Predicate | numberInHilbertList |
P73749
|
FINISHED |
| Object | 17 |
—
|
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: 17 | Statement: [Hilbert’s seventeenth problem, numberInHilbertList, 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInHilbertList Context triple: [Hilbert’s seventeenth problem, numberInHilbertList, 17]
-
A.
positionInHilbertProblems
chosen
Indicates the specific numbered place that a given problem occupies within the list of Hilbert's problems.
-
B.
pillarNumber
Indicates the specific numerical identifier assigned to a particular pillar within a set or structure.
-
C.
honorsNumber
Indicates that one entity formally recognizes or commemorates another by assigning or associating a specific number with it.
-
D.
ordinalNumber
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
-
E.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60abb0748190af41d4e1f419e39c |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:49 p.m.