Triple
T28023976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Boot Record |
E707759
|
entity |
| Predicate | partitionTableOffset |
P171446
|
FINISHED |
| Object | byte 446 |
—
|
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: byte 446 | Statement: [Master Boot Record, partitionTableOffset, byte 446]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partitionTableOffset Context triple: [Master Boot Record, partitionTableOffset, byte 446]
-
A.
partitionTableLocation
Indicates the storage location or path where a specific table partition is physically stored or managed.
-
B.
partitionScheme
Indicates how a whole is divided into distinct parts or segments according to a specific organizing scheme.
-
C.
partitionIVContent
Indicates that one entity divides another entity’s content into distinct parts or sections.
-
D.
positionOnPartition
Indicates that one entity occupies or is located at a specific position along a defined partition or dividing boundary.
-
E.
partitionOf
Indicates that one entity represents a subdivision or component segment of another entity, such that together similar entities collectively form the whole.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 27, 2026, 8:11 p.m.