Triple
T591892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LeNet |
E17289
|
entity |
| Predicate | trainingMethod |
P16019
|
FINISHED |
| Object | supervised 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: supervised learning | Statement: [LeNet, trainingMethod, supervised learning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainingMethod Context triple: [LeNet, trainingMethod, supervised learning]
-
A.
trainingSystem
Indicates a system or framework used to train, instruct, or develop skills or knowledge in a target entity.
-
B.
training
Indicates that one entity is teaching, coaching, or otherwise helping another entity acquire or improve a skill, behavior, or capability.
-
C.
trainingBase
Indicates that one entity serves as the training base, site, or facility where another entity receives training or instruction.
-
D.
typicalTraining
Indicates that an entity commonly undergoes or is associated with a standard or usual form of training in relation to another entity or context.
-
E.
trainingGround
Indicates a location or context where entities engage in practice, drills, or preparation activities to develop or improve skills.
- 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_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. |
| PDg | Predicate description generation | batch_69a4985ada988190aaea628a9b55bca4 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.