Triple
T35627711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CANopen |
E1029498
|
entity |
| Predicate | supportsMapping |
P62523
|
FINISHED |
| Object | PDO mapping |
—
|
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: PDO mapping | Statement: [CANopen, supportsMapping, PDO mapping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMapping Context triple: [CANopen, supportsMapping, PDO mapping]
-
A.
supportsEnvironmentMapping
Indicates that one entity provides or enables environment mapping functionality for another entity or context.
-
B.
supportsMatching
Indicates that one entity provides assistance, resources, or functionality that aligns with or complements another entity’s specific requirements or characteristics.
-
C.
mappingSupportBy
chosen
Indicates that one entity provides support, resources, or functionality enabling another entity to perform or maintain a mapping between elements.
-
D.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
E.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.