Triple
T28027084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAT12 |
E708152
|
entity |
| Predicate | firstTwoFATEntriesReserved |
P200683
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [FAT12, firstTwoFATEntriesReserved, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTwoFATEntriesReserved Context triple: [FAT12, firstTwoFATEntriesReserved, true]
-
A.
partitionTableEntrySize
Indicates the size allocated to or occupied by a single entry in a partition table.
-
B.
standardFloppyDriveSize
Indicates that one entity specifies or is associated with the standard physical size or form factor of a floppy disk drive used by another entity.
-
C.
floppyDiskFormat
Indicates the specific data storage format or standard used on a floppy disk.
-
D.
partitionTableOffset
Indicates the position or displacement of a partition within a table relative to a defined starting point or reference.
-
E.
bootSectorContains
Indicates that the contents of a boot sector include or embed a specified data element or structure.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
| PDg | Predicate description generation | batch_69ffa15c3f348190a59403bc72ac9ed4 |
completed | May 9, 2026, 9:04 p.m. |
Created at: April 27, 2026, 8:13 p.m.