Triple

T3882280
Position Surface form Disambiguated ID Type / Status
Subject Akershus E92851 entity
Predicate survivedAs P22266 FINISHED
Object historical and cultural region after county reform 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: historical and cultural region after county reform | Statement: [Akershus, survivedAs, historical and cultural region after county reform]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: survivedAs
Context triple: [Akershus, survivedAs, historical and cultural region after county reform]
  • A. survivesAs chosen
    Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, another entity.
  • B. survivingFrom
    Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
  • C. survivesIn
    Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
  • D. survivedEvent
    Indicates that an entity continued to live or exist after experiencing and not being destroyed or killed by a particular event.
  • E. survivorWith
    Indicates a relationship where one entity survives an event or condition together with, or in the presence 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_69aed9697de0819087c2559295ff3d12 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69aef1515c688190a38332aedeed8a76 completed March 9, 2026, 4:12 p.m.
PD Predicate disambiguation batch_69aee7574c408190893e70bf80514838 completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:20 p.m.