Triple

T21061787
Position Surface form Disambiguated ID Type / Status
Subject Furst–Saxe–Sipser lower bounds E518865 entity
Predicate depthRestriction P142697 FINISHED
Object constant depth 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: constant depth | Statement: [Furst–Saxe–Sipser lower bounds, depthRestriction, constant depth]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: depthRestriction
Context triple: [Furst–Saxe–Sipser lower bounds, depthRestriction, constant depth]
  • A. dimensionRestriction
    Indicates a constraint or limit imposed on the size, extent, or number of dimensions associated with an entity or relationship.
  • B. depthOrigin
    Indicates the reference point or source location from which the depth of an object or region is measured.
  • C. degreeBound
    Indicates that one entity has a degree or qualification that is formally associated with, limited to, or constrained by another entity (such as an institution, field, or level).
  • D. rangeRestrictedTo
    Indicates that the possible values or targets of a relation are constrained to lie within a specified set or type.
  • E. heightRestriction
    Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
  • 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_69e0b505ef108190b25dd4033e2ff7eb completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6feb064a48190b892b78e27e8d0fa completed April 21, 2026, 4:36 a.m.
PD Predicate disambiguation batch_69e5dbf9d71881908cd85dfc37db93ca completed April 20, 2026, 7:55 a.m.
PDg Predicate description generation batch_69e5e2e03d88819086f8b641656ad8b0 completed April 20, 2026, 8:25 a.m.
Created at: April 16, 2026, 2:38 p.m.