Triple

T466304
Position Surface form Disambiguated ID Type / Status
Subject Crown dependencies E8453 entity
Predicate historicallyDerivedFrom P909 FINISHED
Object medieval possessions of the English Crown 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: medieval possessions of the English Crown | Statement: [Crown dependencies, historicallyDerivedFrom, medieval possessions of the English Crown]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyDerivedFrom
Context triple: [Crown dependencies, historicallyDerivedFrom, medieval possessions of the English Crown]
  • A. historicallyBorneBy
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • B. hasHistoricalOrigin
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • C. historicalOrigin
    Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
  • D. derivedFrom chosen
    Indicates that one entity originates, is obtained, or is developed from another source entity.
  • E. historicallyExtendedBy
    Indicates that something has been continued, expanded, or carried forward over time by another, later entity or development.
  • 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_69a2e7f3aeb48190a19453e3a043f486 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2efd6ec708190b78c7f22deb3ca64 completed Feb. 28, 2026, 1:38 p.m.
PD Predicate disambiguation batch_69a2edea1acc81908a72d9f4c43438ea completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.