Triple
T28027072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAT12 |
E708152
|
entity |
| Predicate | hasBootSectorField |
P31214
|
FINISHED |
| Object | OEM name |
—
|
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: OEM name | Statement: [FAT12, hasBootSectorField, OEM name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBootSectorField Context triple: [FAT12, hasBootSectorField, OEM name]
-
A.
bootSectorContains
chosen
Indicates that the contents of a boot sector include or embed a specified data element or structure.
-
B.
hasMagicNumber
Indicates that an entity is associated with a specific designated "magic" number, often used as a special identifier or constant in a given context.
-
C.
hasVolumeDescriptor
Indicates that something is associated with a qualitative or quantitative description of its volume.
-
D.
isBitField
Indicates that a value, variable, or field is treated as a bit field, meaning its individual bits represent distinct flags or sub-values rather than a single scalar quantity.
-
E.
hasFloppyDrive
Indicates that an entity is equipped with or includes a floppy disk drive.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 27, 2026, 8:13 p.m.