Triple
T15532291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaoqing Ren |
E370248
|
entity |
| Predicate | algorithmTypeWorkedOn |
P21840
|
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: [Shaoqing Ren, algorithmTypeWorkedOn, convolutional neural networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: algorithmTypeWorkedOn Context triple: [Shaoqing Ren, algorithmTypeWorkedOn, convolutional neural networks]
-
A.
algorithmType
chosen
Indicates the specific kind or category of algorithm associated with an entity or process.
-
B.
hasAlgorithmNamedAfter
Indicates that an entity has an algorithm that is named after another entity.
-
C.
algorithmFamily
Indicates that one algorithm belongs to, or is categorized under, a broader family or class of related algorithms.
-
D.
relatedAlgorithm
Indicates that one algorithm has a meaningful connection or association with another algorithm, such as similarity, dependency, or complementary function.
-
E.
algorithmDesigner
Indicates that one entity is responsible for creating or designing algorithms used by another entity or within a particular system.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414877d88190804ee76566004e13 |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.