Triple
T3507214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MNIST |
E74103
|
entity |
| Predicate | benchmarkStatus |
P48400
|
FINISHED |
| Object | canonical toy dataset in machine learning |
—
|
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: canonical toy dataset in machine learning | Statement: [MNIST, benchmarkStatus, canonical toy dataset in machine learning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benchmarkStatus Context triple: [MNIST, benchmarkStatus, canonical toy dataset in machine learning]
-
A.
trainingStatus
Indicates the current state or phase of an entity within a training or learning process.
-
B.
peakStatus
Indicates the condition or phase of something at its highest or most intense point in its progression or lifecycle.
-
C.
benchmarkFor
Indicates that one entity serves as a standard or reference point against which the performance, quality, or characteristics of another entity are measured or evaluated.
-
D.
testStatus
Indicates the current outcome or state of a test, such as whether it has passed, failed, or is still in progress.
-
E.
implementationStatus
Indicates the current state or progress of carrying out or realizing something, such as a plan, design, or requirement.
- F. None of above. chosen
Provenance (4 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf52bd8819085a2ac5f48cc5c68 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:18 p.m.