Triple
T28027107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAT12 |
E708152
|
entity |
| Predicate | typicallyHasNumberOfFATs |
P202175
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [FAT12, typicallyHasNumberOfFATs, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyHasNumberOfFATs Context triple: [FAT12, typicallyHasNumberOfFATs, 2]
-
A.
firstTwoFATEntriesReserved
Indicates that the first two entries in a File Allocation Table (FAT) are reserved and not used for regular data or file allocation.
-
B.
partitionTableEntryCount
Indicates the number of entries contained within a specific partition of a table.
-
C.
raidFormat
Indicates the specific structure or configuration in which a raid (e.g., data storage or coordinated attack) is organized or executed.
-
D.
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.
-
E.
sectorCountPerTrack
Indicates the number of data sectors that are contained on each individual track of a storage medium.
- 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_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
| PDg | Predicate description generation | batch_6a005d86d6e481909e9f6ae81568cfb8 |
completed | May 10, 2026, 10:27 a.m. |
Created at: April 27, 2026, 8:13 p.m.