Triple

T27734145
Position Surface form Disambiguated ID Type / Status
Subject CaseInsensitiveHashCodeProvider E697492 entity
Predicate comparisonIsOrdinal P172119 FINISHED
Object false 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: false | Statement: [CaseInsensitiveHashCodeProvider, comparisonIsOrdinal, false]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: comparisonIsOrdinal
Context triple: [CaseInsensitiveHashCodeProvider, comparisonIsOrdinal, false]
  • 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. isRecursiveOrdinal
    Indicates that an ordinal has the property of being recursive, meaning its order structure can be fully described or generated by a computable (recursive) process.
  • C. isOrderOf
    Indicates that one entity specifies the sequence, arrangement, or ranking in which elements of another entity are organized or occur.
  • D. comparisonRule
    Indicates a rule or criterion that defines how two or more entities are to be compared or evaluated relative to each other.
  • E. isComparisonSort
    Indicates that the sorting algorithm operates by comparing pairs of elements to determine their order.
  • 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_69f6a9603b208190b3533ea2b441514c completed May 3, 2026, 1:48 a.m.
PD Predicate disambiguation batch_69f6a751d5e48190a77dcecbe7ef9f0b completed May 3, 2026, 1:39 a.m.
PDg Predicate description generation batch_69f6a8de0b948190ae333e9cd99cbf6c completed May 3, 2026, 1:46 a.m.
Created at: April 27, 2026, 3:12 p.m.