Triple
T32789400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilbert's tenth problem |
E838585
|
entity |
| Predicate | solutionCollectiveName |
P172101
|
FINISHED |
| Object | MRDP theorem |
—
|
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: MRDP theorem | Statement: [Hilbert's tenth problem, solutionCollectiveName, MRDP theorem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solutionCollectiveName Context triple: [Hilbert's tenth problem, solutionCollectiveName, MRDP theorem]
-
A.
usedCollectiveName
Indicates that a group of entities is referred to by a shared collective name.
-
B.
collectiveForm
Indicates that an entity represents a collective or group form derived from or composed of multiple individual entities.
-
C.
collectiveNameForm
chosen
Indicates that one entity serves as the collective or group name form used to refer to multiple members of another entity or class.
-
D.
collectiveBody
Indicates that multiple individuals are grouped and act together as a single collective entity or body.
-
E.
formerCollective
Indicates a relationship where an entity was once part of a collective group or organization but is no longer a member.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:14 a.m.