Triple
T591904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LeNet |
E17289
|
entity |
| Predicate | learningParadigm |
P779
|
FINISHED |
| Object | end-to-end 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: end-to-end learning | Statement: [LeNet, learningParadigm, end-to-end learning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: learningParadigm Context triple: [LeNet, learningParadigm, end-to-end learning]
-
A.
educationalModel
Indicates that one entity serves as an educational model, framework, or paradigm that guides or structures the teaching, learning, or training practices of another entity.
-
B.
trainingSystem
Indicates a system or framework used to train, instruct, or develop skills or knowledge in a target entity.
-
C.
educationalApproach
chosen
Indicates the method, strategy, or philosophy used to guide teaching and learning within an educational context.
-
D.
educationalFocus
Indicates the primary subject area or theme that an educational activity, program, or resource is centered on.
-
E.
educationSystem
Indicates the relationship in which an entity is part of, governed by, or operates within a particular system or structure of education.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bbaf53081908eed240bed09f63b |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.