Triple

T27734115
Position Surface form Disambiguated ID Type / Status
Subject CaseInsensitiveComparer E697491 entity
Predicate defaultComparisonType P170978 FINISHED
Object culture-sensitive, case-insensitive 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: culture-sensitive, case-insensitive | Statement: [CaseInsensitiveComparer, defaultComparisonType, culture-sensitive, case-insensitive]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defaultComparisonType
Context triple: [CaseInsensitiveComparer, defaultComparisonType, culture-sensitive, case-insensitive]
  • A. comparisonType
    Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
  • B. isComparisonSort
    Indicates that the sorting algorithm operates by comparing pairs of elements to determine their order.
  • C. invariantComparisonType
    Indicates the specific way in which two invariants are compared or evaluated relative to each other.
  • D. comparisonMethod
    Indicates the method or criteria used to compare two or more entities or values.
  • E. primaryComparison
    Indicates that one entity is being used as the main reference point or standard against which another entity is compared.
  • 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_69ef590c3e288190ad54d2465af8ca4e completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f6984bb55c8190862eb8796868d188 completed May 3, 2026, 12:35 a.m.
PD Predicate disambiguation batch_69f69661e6ec8190948251c7516a32ad completed May 3, 2026, 12:27 a.m.
PDg Predicate description generation batch_69f6978ec27c8190a488e1f9c2566d38 completed May 3, 2026, 12:32 a.m.
Created at: April 27, 2026, 3:12 p.m.