Triple
T30358096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EF lens mount |
E772200
|
entity |
| Predicate | focusDrive |
P4169
|
FINISHED |
| Object | in-lens motor |
—
|
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: in-lens motor | Statement: [Canon EF lens mount, focusDrive, in-lens motor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusDrive Context triple: [Canon EF lens mount, focusDrive, in-lens motor]
-
A.
focusDriveSupport
Indicates that an entity provides support or functionality specifically aimed at enhancing or enabling another entity’s focus or concentration.
-
B.
driveContext
Indicates that one entity is operating or controlling a vehicle or mode of transport within a particular situational or environmental context.
-
C.
drivingFocus
Indicates that one entity serves as the primary motivating force, priority, or central concern guiding another entity’s actions or decisions.
-
D.
driveResult
Indicates the outcome or consequence produced by a driving action or driving-related event.
-
E.
driveType
chosen
Indicates the type or configuration of the drive mechanism used to power or propel an 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 7:57 p.m.