Triple
T10023685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auto-Encoding Variational Bayes |
E200670
|
entity |
| Predicate | arXivCategory |
P3397
|
FINISHED |
| Object | stat.ML |
—
|
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: stat.ML | Statement: [Auto-Encoding Variational Bayes, arXivCategory, stat.ML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arXivCategory Context triple: [Auto-Encoding Variational Bayes, arXivCategory, stat.ML]
-
A.
arxivId
Indicates that an entity (such as a paper or work) is associated with a specific arXiv identifier used to reference it in the arXiv repository.
-
B.
mathematicalSubjectClassification
Indicates that one entity classifies the mathematical subject area or field to which another entity (such as a work, concept, or topic) belongs.
-
C.
citationCategory
Indicates the type or role of a citation in relation to the referenced work (e.g., background, support, contrast, or extension).
-
D.
researchClassification
chosen
Indicates that an entity is assigned a specific category or type within a research-related classification scheme.
-
E.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd7c75548190aa604d90d63dc111 |
completed | April 2, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:53 p.m.