Triple
T18770659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Sierra Format |
E459008
|
entity |
| Predicate | volumeDescriptorLocation |
P62335
|
FINISHED |
| Object | logical block 16 |
—
|
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: logical block 16 | Statement: [High Sierra Format, volumeDescriptorLocation, logical block 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volumeDescriptorLocation Context triple: [High Sierra Format, volumeDescriptorLocation, logical block 16]
-
A.
hasVolumeDescriptor
Indicates that something is associated with a qualitative or quantitative description of its volume.
-
B.
mountingLocation
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
C.
volumeIdentifierLengthLimit
Indicates the maximum allowed length for a volume’s identifier within a given system or context.
-
D.
foundInVolume
Indicates that one entity is physically or logically contained within, or occurs in, a specific volume (such as a book volume, data volume, or bounded collection).
-
E.
metadataLocation
chosen
Indicates the location or source where descriptive or administrative information about an entity is stored or can be accessed.
- 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_69e59335a01881908731371be1e27a6b |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.