Triple

T18497858
Position Surface form Disambiguated ID Type / Status
Subject Canadian Heraldic Authority E451993 entity
Predicate recordsAre P63826 FINISHED
Object maintained in perpetuity 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: maintained in perpetuity | Statement: [Canadian Heraldic Authority, recordsAre, maintained in perpetuity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recordsAre
Context triple: [Canadian Heraldic Authority, recordsAre, maintained in perpetuity]
  • A. recordsType
    Indicates that one entity documents, stores, or keeps an official account of a particular type or category of information, event, or item.
  • B. recordDetail
    Indicates that one entity stores or documents specific information or attributes about another entity.
  • C. areRecordedBy
    Indicates that an event, observation, or piece of information is captured or documented by a specific recording agent, device, or process.
  • D. recordStatus chosen
    Indicates the current state or condition of a record within a system or process (e.g., active, inactive, pending, or archived).
  • E. recordsOnAppeal
    Indicates that certain records or documents are included in, or pertain to, the official record for an appeal in a legal or administrative proceeding.
  • 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_69d8d3855d50819097fc8561b0299dd9 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e532c15dec8190941e7c7a4cdebb66 completed April 19, 2026, 7:53 p.m.
PD Predicate disambiguation batch_69e469dbf5208190b6fc49e02a087f54 completed April 19, 2026, 5:36 a.m.
Created at: April 10, 2026, 11:36 a.m.