Triple

T2575993
Position Surface form Disambiguated ID Type / Status
Subject United States Attorneys' Manual E57775 entity
Predicate notBindingOn P28391 FINISHED
Object courts 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: courts | Statement: [United States Attorneys' Manual, notBindingOn, courts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notBindingOn
Context triple: [United States Attorneys' Manual, notBindingOn, courts]
  • A. isNotBindingOn chosen
    Indicates that an agreement, rule, or obligation does not have legal or enforceable effect on the referenced entity.
  • B. bindingOn
    Indicates that one party is legally or formally obligated to follow, accept, or be governed by a decision, rule, or agreement established by another.
  • C. isNonBinding
    Indicates that the relationship or agreement exists but does not create any legally or formally enforceable obligation between the involved entities.
  • D. notObservedBy
    Indicates that an entity, event, or condition is not detected, recorded, or perceived by a specified observer or observation process.
  • E. notObservedIn
    Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
  • 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_69ab4a51410081908501dcf8bad9adc4 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd3a606e481909bcea46de468bb99 completed March 7, 2026, 7:28 a.m.
PD Predicate disambiguation batch_69abd0ce4dcc8190b17a65abf9bd1bb0 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:49 p.m.