Triple
T29636268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contrastive Predictive Coding |
E755722
|
entity |
| Predicate | canUseBackbone |
P9928
|
FINISHED |
| Object | convolutional neural networks |
—
|
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: convolutional neural networks | Statement: [Contrastive Predictive Coding, canUseBackbone, convolutional neural networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseBackbone Context triple: [Contrastive Predictive Coding, canUseBackbone, convolutional neural networks]
-
A.
isCombinationBackboneWith
Indicates a structural relationship where one entity serves as a backbone or core framework that is combined with another entity to form a composite or integrated whole.
-
B.
backboneType
Indicates the structural configuration or category of backbone that characterizes or supports an entity.
-
C.
canBeBackedBy
Indicates that one entity is capable of being supported, guaranteed, or secured by another entity.
-
D.
canUse
chosen
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
E.
hasBackend
Indicates that one entity functions as the backend or server-side component that supports or powers another entity.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 6:44 p.m.