Triple
T8175385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTFS |
E190925
|
entity |
| Predicate | fileNameLengthLimit |
P31494
|
FINISHED |
| Object | 255 characters |
—
|
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: 255 characters | Statement: [NTFS, fileNameLengthLimit, 255 characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileNameLengthLimit Context triple: [NTFS, fileNameLengthLimit, 255 characters]
-
A.
fileNameLimit
Indicates a constraint or maximum allowed length or format for a file’s name in a given context.
-
B.
maximumFileNameLength
chosen
Indicates the maximum number of characters allowed in a file name within a given system or context.
-
C.
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.
-
D.
volumeNameLengthLimit
Indicates the maximum allowed length for a volume’s name in this context.
-
E.
volumeIdentifierLengthLimit
Indicates the maximum allowed length for a volume’s identifier within a given 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4ab8295081909a450fcaa34f6ec6 |
completed | March 31, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.