Triple

T24080924
Position Surface form Disambiguated ID Type / Status
Subject Maryland Public Safety Article E596500 entity
Predicate isBindingIn P154773 FINISHED
Object State of Maryland NE NERFINISHED

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: State of Maryland | Statement: [Maryland Public Safety Article, isBindingIn, State of Maryland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isBindingIn
Context triple: [Maryland Public Safety Article, isBindingIn, State of Maryland]
  • A. isNotBindingOn
    Indicates that an agreement, rule, or obligation does not have legal or enforceable effect on the referenced entity.
  • B. isInitiallyBoundWith
    Indicates that two or more entities are connected, associated, or constrained together at the starting point of a process, state, or interaction.
  • C. isNonBinding
    Indicates that the relationship or agreement exists but does not create any legally or formally enforceable obligation between the involved entities.
  • D. bindsTo
    Indicates that one entity physically or functionally attaches or connects to another, often with some specificity or selectivity in the interaction.
  • E. areBoundFrom
    Indicates that one entity is constrained, limited, or restricted starting from a specified point, source, or condition.
  • 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_69e288c3999c8190809b282a04813dec completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1dc2351e08190857d57f266d1d4bf completed April 29, 2026, 10:23 a.m.
PD Predicate disambiguation batch_69f1764b1d4c8190b12590c6339c31c1 completed April 29, 2026, 3:08 a.m.
PDg Predicate description generation batch_69f1785afe3c81909be28986ffe944bf completed April 29, 2026, 3:17 a.m.
Created at: April 17, 2026, 10:43 p.m.