Triple
T15361551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIFAR-100 |
E367299
|
entity |
| Predicate | hasCanonicalURL |
P27862
|
FINISHED |
| Object | https://www.cs.toronto.edu/~kriz/cifar.html |
—
|
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: https://www.cs.toronto.edu/~kriz/cifar.html | Statement: [CIFAR-100, hasCanonicalURL, https://www.cs.toronto.edu/~kriz/cifar.html]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalURL Context triple: [CIFAR-100, hasCanonicalURL, https://www.cs.toronto.edu/~kriz/cifar.html]
-
A.
hasCanonicalReference
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
B.
hasCanonicalLocation
chosen
Indicates that an entity is associated with its primary, standard, or officially recognized location.
-
C.
hasCanonicalRelevance
Indicates that something is considered standard, authoritative, or centrally important within an established canon or reference framework.
-
D.
hasCanonicalRepresentation
Indicates that one entity is the standard or authoritative form in which another entity is represented.
-
E.
hasCanonicalContext
Indicates that something is associated with its primary, standard, or officially recognized contextual setting or framework.
- 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_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. |
Created at: April 10, 2026, 3:18 a.m.