Triple

T1724481
Position Surface form Disambiguated ID Type / Status
Subject ext4 E37465 entity
Predicate supportsCaseSensitiveFilenames P31209 FINISHED
Object true 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: true | Statement: [ext4, supportsCaseSensitiveFilenames, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsCaseSensitiveFilenames
Context triple: [ext4, supportsCaseSensitiveFilenames, true]
  • A. isCaseInsensitiveInStandard
    Indicates that the comparison, matching, or evaluation of values is performed without distinguishing between uppercase and lowercase characters according to a defined standard.
  • B. hasCaseInflection
    Indicates that a word or phrase changes form to reflect grammatical case (such as nominative, accusative, etc.) in a given language context.
  • C. caseSensitivityVariant
    Indicates that one string or textual form is a variant of another that differs only in letter casing (e.g., uppercase vs lowercase).
  • D. hasCase
    Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
  • E. hasCaseForms
    Indicates that an entity possesses multiple grammatical case variants or inflected forms associated with it.
  • 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_69a8861acab88190bb43cde203429399 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aadb7bda1081908f2c41c520c9c55c completed March 6, 2026, 1:49 p.m.
PD Predicate disambiguation batch_69aa61c0a0288190bce9d60062a84b69 completed March 6, 2026, 5:10 a.m.
PDg Predicate description generation batch_69aadb68868c819097ec6db6194abae6 completed March 6, 2026, 1:49 p.m.
Created at: March 4, 2026, 7:30 p.m.