Triple
T15361519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIFAR-100 |
E367299
|
entity |
| Predicate | hasFineGrainedClasses |
P118267
|
FINISHED |
| Object | 100 |
—
|
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: 100 | Statement: [CIFAR-100, hasFineGrainedClasses, 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFineGrainedClasses Context triple: [CIFAR-100, hasFineGrainedClasses, 100]
-
A.
hasMultipleSubclasses
Indicates that a class or category is related to more than one distinct subclass within a hierarchy.
-
B.
hasTwoClasses
Indicates that an entity is associated with exactly two distinct classes or categories.
-
C.
hasShareClass
Indicates that an entity is associated with a specific class or category of shares that defines distinct rights or characteristics of ownership.
-
D.
usesClassifiers
Indicates that one entity employs or relies on a system of classifiers (such as category labels or measure words) when referring to or organizing another entity.
-
E.
hasFeatureClass
Indicates that an entity is associated with, or categorized under, a particular feature class that characterizes its type or nature.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e4607408190ab281a7f7a8012d3 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:18 a.m.