Triple

T12609102
Position Surface form Disambiguated ID Type / Status
Subject Ricercar a 3 E301063 entity
Predicate relativeComplexityComparedTo P25304 FINISHED
Object less complex than Ricercar a 6 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: less complex than Ricercar a 6 | Statement: [Ricercar a 3, relativeComplexityComparedTo, less complex than Ricercar a 6]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relativeComplexityComparedTo
Context triple: [Ricercar a 3, relativeComplexityComparedTo, less complex than Ricercar a 6]
  • A. hasComplexity
    Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
  • B. hasReasoningComplexity
    Indicates that an action, process, or decision involves a certain level or type of cognitive or logical complexity in its reasoning.
  • C. typicalComplexity
    Indicates the usual or characteristic level of complexity associated with an entity, process, or situation.
  • D. parsingComplexity
    Indicates the level of difficulty or computational effort required to parse or analyze a given input or structure.
  • E. relativeLevel chosen
    Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of another entity.
  • 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_69d7bdea2ca881908f379526c13b1145 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9559458dc8190bc4d6e697e99d70e completed April 10, 2026, 7:55 p.m.
PD Predicate disambiguation batch_69d9541894fc8190a0c3706a414279f0 completed April 10, 2026, 7:48 p.m.
Created at: April 9, 2026, 5:11 p.m.