Triple
T31946182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R1 button |
E815656
|
entity |
| Predicate | standardMapping |
P42091
|
FINISHED |
| Object | right bumper |
—
|
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: right bumper | Statement: [R1 button, standardMapping, right bumper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardMapping Context triple: [R1 button, standardMapping, right bumper]
-
A.
typicalMapping
chosen
Indicates a standard or commonly used correspondence between elements of one set, structure, or representation and those of another.
-
B.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
C.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
-
D.
standardReference
Indicates that one entity serves as the authoritative or canonical reference or benchmark for interpreting, validating, or comparing another entity.
-
E.
standardUse
Indicates that something is used in a typical, expected, or officially accepted manner for its intended purpose.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 12:06 a.m.