Triple

T26966633
Position Surface form Disambiguated ID Type / Status
Subject EXPTIME E679188 entity
Predicate upperBoundFor P14327 FINISHED
Object problems solvable by exhaustive search over exponentially many configurations 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: problems solvable by exhaustive search over exponentially many configurations | Statement: [EXPTIME, upperBoundFor, problems solvable by exhaustive search over exponentially many configurations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: upperBoundFor
Context triple: [EXPTIME, upperBoundFor, problems solvable by exhaustive search over exponentially many configurations]
  • A. isUpperBoundFor chosen
    Indicates that one value is greater than or equal to every element in a given set or collection, serving as an upper limit for them.
  • B. includesUpperBound
    Indicates that the specified range or interval contains and counts its upper limit value as part of the set.
  • C. upperBoundaryType
    Indicates the kind or classification of the upper boundary that limits or caps a given range, interval, or extent.
  • D. upperLimit
    Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
  • E. boundedSuperiorlyBy
    Indicates that one entity serves as the upper or top boundary limit 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_69eeeb4f3a448190b1e94b2d4776c16e completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f621210b788190ab9e910cd635f366 completed May 2, 2026, 4:06 p.m.
PD Predicate disambiguation batch_69f611af72ac819094598dd2530d7411 completed May 2, 2026, 3:01 p.m.
Created at: April 27, 2026, 6:36 a.m.