Triple
T28027088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAT12 |
E708152
|
entity |
| Predicate | longFilenamesViaVFAT |
P31213
|
FINISHED |
| Object | possible |
—
|
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: possible | Statement: [FAT12, longFilenamesViaVFAT, possible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longFilenamesViaVFAT Context triple: [FAT12, longFilenamesViaVFAT, possible]
-
A.
supportsLongFilenames
Indicates that an entity is capable of handling, storing, or processing filenames that exceed a standard or traditional length limit.
-
B.
storesLongFilenamesIn
Indicates that an entity is capable of saving or maintaining long filenames within a specified storage medium or structure.
-
C.
longFilenameSupportAddedIn
chosen
Indicates that support for long filenames was introduced or enabled in a specified system, version, or context.
-
D.
maximumFileNameLength
Indicates the maximum number of characters allowed in a file name within a given system or context.
-
E.
shortFileNameLimit
Indicates that there is a maximum allowed length or size constraint on a file’s short (truncated or legacy) name within a system or context.
- 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_69f63c6ef4348190821f991c682a6894 |
completed | May 2, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:13 p.m.