Triple
T18770519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primary Volume Descriptor |
E459005
|
entity |
| Predicate | standardIdentifierValue |
P3732
|
FINISHED |
| Object | CD001 |
—
|
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: CD001 | Statement: [Primary Volume Descriptor, standardIdentifierValue, CD001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardIdentifierValue Context triple: [Primary Volume Descriptor, standardIdentifierValue, CD001]
-
A.
standardNumberStandardizedBy
Indicates that a standard number has been formally defined, approved, or regulated by a specific standardizing authority or organization.
-
B.
standardIdentity
Indicates that two entities are considered equivalent or identical according to a defined standard or canonical form.
-
C.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
D.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
E.
identifierStability
Indicates that an identifier maintains a consistent, unchanging reference to the same entity over time or across different contexts.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d8782b4819080513fb46798c4db |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.