Triple
T25130539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letters to a Young Mathematician |
E629510
|
entity |
| Predicate | nonTechnical |
P71599
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Letters to a Young Mathematician, nonTechnical, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonTechnical Context triple: [Letters to a Young Mathematician, nonTechnical, true]
-
A.
isNonTechnical
chosen
Indicates that an entity, role, or context does not involve technical skills, knowledge, or specialized technical responsibilities.
-
B.
nonProfessional
Indicates that the relationship or activity is carried out in an informal or amateur capacity rather than as part of a recognized profession or paid occupation.
-
C.
nonGovernmental
Indicates that an entity, action, or relationship is not associated with, controlled by, or part of a government or governmental body.
-
D.
nonClerical
Indicates that an entity, role, or activity is not related to clerical or administrative work or duties.
-
E.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465f79bd081909a2f5165aa89dc16 |
completed | May 1, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:28 a.m.