Triple
T29901157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Be File System |
E759409
|
entity |
| Predicate | fileNameCaseSensitivity |
P31209
|
FINISHED |
| Object | case-sensitive |
—
|
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: case-sensitive | Statement: [Be File System, fileNameCaseSensitivity, case-sensitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileNameCaseSensitivity Context triple: [Be File System, fileNameCaseSensitivity, case-sensitive]
-
A.
supportsCaseSensitiveFilenames
chosen
Indicates that the subject is capable of handling or distinguishing filenames based on letter casing, treating differently cased names as distinct.
-
B.
fileNameCase
Indicates how the letter casing (such as upper, lower, or mixed case) is used or required in a file name.
-
C.
isCaseSensitiveInStandard
Indicates that the interpretation or comparison of the entity follows a standard in which letter case differences are treated as significant.
-
D.
caseSensitivityVariant
Indicates that one string or textual form is a variant of another that differs only in letter casing (e.g., uppercase vs lowercase).
-
E.
hasCaseInflection
Indicates that a word or phrase changes form to reflect grammatical case (such as nominative, accusative, etc.) in a given language 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6772ecd788190acfe7c583599b3c1 |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:06 p.m.