Triple

T13653541
Position Surface form Disambiguated ID Type / Status
Subject Bounding Theory E326798 entity
Predicate imposesConstraintOn P7925 FINISHED
Object movement across clause boundaries 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: movement across clause boundaries | Statement: [Bounding Theory, imposesConstraintOn, movement across clause boundaries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: imposesConstraintOn
Context triple: [Bounding Theory, imposesConstraintOn, movement across clause boundaries]
  • A. constrainedBy
    Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
  • B. designedToConstrain
    Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
  • C. imposedOn
    Indicates that one party enforces, applies, or places a requirement, burden, or constraint onto another party or entity.
  • D. imposes chosen
    Indicates that one entity enforces, applies, or places a rule, condition, burden, or obligation upon another entity.
  • E. hasConstraintOnSupport
    Indicates that one entity imposes a limitation, requirement, or condition on the type, amount, or manner of support that another entity can provide or receive.
  • 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_69d8076d8270819092afc2f0e9c359a8 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc60ace048190a4b92310ba272bd1 completed April 12, 2026, 4:19 p.m.
PD Predicate disambiguation batch_69dbbe8a027081908d8f884b89707a5e completed April 12, 2026, 3:47 p.m.
Created at: April 9, 2026, 9:52 p.m.