Triple
T31317159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USBMR1400128 |
E798626
|
entity |
| Predicate | componentRegistrantCode |
P188796
|
FINISHED |
| Object | BMR |
—
|
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: BMR | Statement: [USBMR1400128, componentRegistrantCode, BMR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentRegistrantCode Context triple: [USBMR1400128, componentRegistrantCode, BMR]
-
A.
codenameComponent
Indicates that one entity serves as the codename or code-designation assigned to another entity as its component or identifying label.
-
B.
configurationCode
Indicates that an entity is associated with a specific configuration identifier or code that defines its setup or settings.
-
C.
codeComponent1
Indicates that one entity is a specific code component (such as a function, class, or module) within a software system.
-
D.
definesComponent
Indicates that one entity specifies or establishes the structure, behavior, or characteristics of another entity as its component.
-
E.
commissioningComponent
Indicates that one entity is responsible for initiating, authorizing, or overseeing the creation or execution of another entity or activity.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbad1b3ba08190ad69e21461333f2e |
completed | May 6, 2026, 9:05 p.m. |
Created at: April 29, 2026, 9:15 p.m.