Triple
T28023992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Boot Record |
E707759
|
entity |
| Predicate | partitionEntryAddressing |
P64006
|
FINISHED |
| Object | CHS |
—
|
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: CHS | Statement: [Master Boot Record, partitionEntryAddressing, CHS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partitionEntryAddressing Context triple: [Master Boot Record, partitionEntryAddressing, CHS]
-
A.
partitionScheme
Indicates how a whole is divided into distinct parts or segments according to a specific organizing scheme.
-
B.
partitionTableEntrySize
Indicates the size allocated to or occupied by a single entry in a partition table.
-
C.
addressingMechanism
chosen
Indicates the method or system used to identify, locate, or reference a target within a larger space, network, or structure.
-
D.
sectionAddressed
Indicates that a specific section or part of a document, text, or resource is being referred to, targeted, or dealt with by an action or statement.
-
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.
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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 8:11 p.m.