Triple
T18770518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primary Volume Descriptor |
E459005
|
entity |
| Predicate | hasVolumeDescriptorTypeValue |
P20330
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Primary Volume Descriptor, hasVolumeDescriptorTypeValue, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolumeDescriptorTypeValue Context triple: [Primary Volume Descriptor, hasVolumeDescriptorTypeValue, 1]
-
A.
hasVolumeDescriptor
chosen
Indicates that something is associated with a qualitative or quantitative description of its volume.
-
B.
hasThreeVolumeStructureRole
Indicates that an entity participates in or fulfills a role within a three-volume structural organization or framework.
-
C.
hasVaultType
Indicates that an entity is associated with or classified by a particular type or category of vault.
-
D.
hasSizeDescriptor
Indicates that an entity is associated with a qualitative description of its size (e.g., small, large, huge).
-
E.
typeOfLevelDescriptor
Indicates that one entity serves as a descriptor or classification label specifying the type or category of a particular level associated with another 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_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.