Triple
T29968995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilbert’s nineteenth problem |
E761265
|
entity |
| Predicate | currentCategory |
P29075
|
FINISHED |
| Object | resolved problem in mathematics |
—
|
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: resolved problem in mathematics | Statement: [Hilbert’s nineteenth problem, currentCategory, resolved problem in mathematics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentCategory Context triple: [Hilbert’s nineteenth problem, currentCategory, resolved problem in mathematics]
-
A.
activeCategory
Indicates that an entity currently belongs to or is associated with a category that is marked as active or in use.
-
B.
catalogCategory
Indicates that an item or entity is assigned to, or belongs within, a specific catalog category.
-
C.
canonicalCategory
chosen
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
D.
viewCategory
Indicates that an entity views or accesses a particular category (such as a group, type, or classification of items or content).
-
E.
sampleCategory
Indicates that an item or instance belongs to, or is classified under, a particular sample category.
- 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_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 29, 2026, 6:31 p.m.