Triple

T4557735
Position Surface form Disambiguated ID Type / Status
Subject Test Act 1673 E120519 entity
Predicate appliedToOfficeType P1129 FINISHED
Object civil offices 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: civil offices | Statement: [Test Act 1673, appliedToOfficeType, civil offices]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliedToOfficeType
Context triple: [Test Act 1673, appliedToOfficeType, civil offices]
  • A. hasOfficeType
    Indicates that an entity’s office is classified as a specific type or category of office.
  • B. usedByOffice
    Indicates that something is utilized, operated, or employed by an office or office-related entity.
  • C. supportsOffice
    Indicates that one entity provides assistance, resources, or endorsement to an office or officeholder in performing its functions or maintaining its operations.
  • D. relatesToOffice
    Indicates that one entity has a connection, association, or relevance to an office, its functions, or its environment.
  • E. appliesTo chosen
    Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
  • 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_69bd4636f1648190a701445c2fcd9c17 completed March 20, 2026, 1:05 p.m.
NER Named-entity recognition batch_69bd58163e6081909d5a3aae12c42a00 completed March 20, 2026, 2:22 p.m.
PD Predicate disambiguation batch_69bd52254c648190a5144cfe8fa7e409 completed March 20, 2026, 1:56 p.m.
Created at: March 20, 2026, 1:09 p.m.