Triple

T2339761
Position Surface form Disambiguated ID Type / Status
Subject Crown in right of each Commonwealth realm E44995 entity
Predicate canEnterInto P5772 FINISHED
Object contracts on behalf of the state 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: contracts on behalf of the state | Statement: [Crown in right of each Commonwealth realm, canEnterInto, contracts on behalf of the state]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canEnterInto
Context triple: [Crown in right of each Commonwealth realm, canEnterInto, contracts on behalf of the state]
  • A. mayEnter
    Indicates that one entity is permitted or authorized to enter or access another entity or location.
  • B. canPass
    Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
  • C. canEnterIntoAgreementsWith chosen
    Indicates that one entity has the legal or formal capacity to make binding agreements or contracts with another entity.
  • D. hasEntrance
    Indicates that one entity possesses or provides an entry point or access way to another entity or space.
  • E. hasEntranceOn
    Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature 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_69a88917935081909b755dbf38e81024 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abc6f75d888190a2e41edaa532e83f completed March 7, 2026, 6:34 a.m.
PD Predicate disambiguation batch_69abc594087c819098100a10c5478a4b completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:52 p.m.