Triple
T31131184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 12.0 |
E793510
|
entity |
| Predicate | hasCaseFoldingDataFile |
P196827
|
FINISHED |
| Object | CaseFolding.txt version 12.0.0 |
—
|
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: CaseFolding.txt version 12.0.0 | Statement: [Unicode 12.0, hasCaseFoldingDataFile, CaseFolding.txt version 12.0.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaseFoldingDataFile Context triple: [Unicode 12.0, hasCaseFoldingDataFile, CaseFolding.txt version 12.0.0]
-
A.
hasCaseInflection
Indicates that a word or phrase changes form to reflect grammatical case (such as nominative, accusative, etc.) in a given language context.
-
B.
supportsCaseSensitiveFilenames
Indicates that the subject is capable of handling or distinguishing filenames based on letter casing, treating differently cased names as distinct.
-
C.
hasCaseForms
Indicates that an entity possesses multiple grammatical case variants or inflected forms associated with it.
-
D.
hasUnicodeVariant
Indicates that one entity has an alternative representation or equivalent form in Unicode corresponding to the other entity.
-
E.
isCaseSensitiveInStandard
Indicates that the interpretation or comparison of the entity follows a standard in which letter case differences are treated as significant.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
| PDg | Predicate description generation | batch_69fe6b7a823881909dc2037fe25bea24 |
completed | May 8, 2026, 11:02 p.m. |
Created at: April 29, 2026, 9:05 p.m.