Triple
T29968943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilbert’s sixteenth problem |
E761264
|
entity |
| Predicate | numberInList |
P198020
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [Hilbert’s sixteenth problem, numberInList, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInList Context triple: [Hilbert’s sixteenth problem, numberInList, 16]
-
A.
containsNumber
Indicates that one entity includes or has at least one numeric value or digit within it.
-
B.
hasNumberInGroup
chosen
Indicates that an entity is associated with a specific numerical value that identifies its position, count, or role within a particular group.
-
C.
isListOf
Indicates that one entity is a collection or sequence whose elements are instances or members of another specified entity.
-
D.
isNumberInAct
Indicates that a specific number appears within, or is associated with, a particular act (such as a legal act, play act, or similar structured unit).
-
E.
includesList
Indicates that one entity contains or encompasses a specified list of other entities as its elements or members.
- 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_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
Created at: April 29, 2026, 6:31 p.m.