Triple
T28023514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAT |
E707749
|
entity |
| Predicate | FAT32MaxFileSize |
P31204
|
FINISHED |
| Object | 4 GB minus 1 byte |
—
|
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: 4 GB minus 1 byte | Statement: [FAT, FAT32MaxFileSize, 4 GB minus 1 byte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FAT32MaxFileSize Context triple: [FAT, FAT32MaxFileSize, 4 GB minus 1 byte]
-
A.
maxFileSize
chosen
Indicates the maximum allowable size limit for a file in the given context.
-
B.
fileNameLimit
Indicates a constraint or maximum allowed length or format for a file’s name in a given context.
-
C.
maximumFileNameLength
Indicates the maximum number of characters allowed in a file name within a given system or context.
-
D.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
-
E.
hasMaxMBsPerFrameExample
Indicates that there is a specified maximum number of macroblocks allowed per frame in the given example.
- 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_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:11 p.m.