Triple
T29484826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linnik’s theorem on the least prime in an arithmetic progression |
E747889
|
entity |
| Predicate | hasRefinementsBy |
P112260
|
FINISHED |
| Object | Heath-Brown |
—
|
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: Heath-Brown | Statement: [Linnik’s theorem on the least prime in an arithmetic progression, hasRefinementsBy, Heath-Brown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRefinementsBy Context triple: [Linnik’s theorem on the least prime in an arithmetic progression, hasRefinementsBy, Heath-Brown]
-
A.
hasRefinement
Indicates that one entity represents a more detailed, specific, or improved version of another entity.
-
B.
hasFacet
Indicates that an entity possesses a particular aspect, side, or dimension as one of its distinguishable parts or characteristics.
-
C.
refinementBy
chosen
Indicates that one entity serves as a more detailed, precise, or improved version of another entity.
-
D.
hasRefiningOperations
Indicates that one entity performs or is associated with refining processes or operations applied to another entity.
-
E.
hasFilterSet
Indicates that a filter configuration has been applied or associated with a given entity or context.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
Created at: April 28, 2026, 4:07 p.m.