Triple
T737838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Neumann algebra |
E14972
|
entity |
| Predicate | classificationBy |
P6736
|
FINISHED |
| Object | type decomposition |
—
|
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: type decomposition | Statement: [von Neumann algebra, classificationBy, type decomposition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationBy Context triple: [von Neumann algebra, classificationBy, type decomposition]
-
A.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
-
B.
classificationSystem
chosen
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
-
C.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
D.
previousClassification
Indicates that one classification precedes another in time or in an ordered sequence of classifications.
-
E.
rankingCategory
Indicates the classification or type of ranking under which an entity is evaluated or ordered.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fc734c81908fbd36386d5746d6 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.