Triple

T12014995
Position Surface form Disambiguated ID Type / Status
Subject Regent of Scotland E286001 entity
Predicate reasonForAppointment P102792 FINISHED
Object monarch’s minority 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: monarch’s minority | Statement: [Regent of Scotland, reasonForAppointment, monarch’s minority]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForAppointment
Context triple: [Regent of Scotland, reasonForAppointment, monarch’s minority]
  • A. appointmentType
    Indicates the specific category or nature of an appointment associated with an entity or event.
  • B. requiresForHeadAppointment
    Indicates that a certain condition, qualification, or prior role must be fulfilled in order for an entity to be appointed as the head of something.
  • C. reasonForStay
    Indicates the underlying cause, purpose, or circumstance that explains why an entity remains or is staying in a particular place or situation.
  • D. reasonForTime
    Indicates that one entity provides the explanation or cause for a particular point or duration of time associated with another entity.
  • E. reasonForWork
    Indicates that one entity specifies the motivation, cause, or purpose behind another entity’s work or activity.
  • 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_69d6ab45a368819084fce08bf0dc3705 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9100b4ca8819084845ca4c13e34ce completed April 10, 2026, 2:58 p.m.
PD Predicate disambiguation batch_69d902b6ebbc8190b13c44a61c6f81b9 completed April 10, 2026, 2:01 p.m.
PDg Predicate description generation batch_69d91006e14081909838412df082f794 completed April 10, 2026, 2:58 p.m.
Created at: April 8, 2026, 9:47 p.m.