Triple

T37364137
Position Surface form Disambiguated ID Type / Status
Subject Lyminge E927661 entity
Predicate earliestChristianFoundation P156005 FINISHED
Object one of the earliest in Kent 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: one of the earliest in Kent | Statement: [Lyminge, earliestChristianFoundation, one of the earliest in Kent]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: earliestChristianFoundation
Context triple: [Lyminge, earliestChristianFoundation, one of the earliest in Kent]
  • A. isOldestSurvivingChurchIn
    Indicates that a church is the most ancient one still standing within a specified location or region.
  • B. earliestChristianSiteComponent chosen
    Indicates that one entity is the earliest-known Christian site component in relation to another, typically within a given location or architectural context.
  • C. eraOfFoundation
    Indicates the specific historical era or time period during which an entity was founded.
  • D. hasAncientChristianHeritage
    Indicates that an entity possesses a historical connection to early or longstanding Christian traditions, communities, or influences.
  • E. firstChapelBuilt
    Indicates that the subject is the location or entity where the first chapel was constructed or established.
  • 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_69f76eb701788190b40824bc4594d985 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd0b92f42881908cd77e3f058adcc2 completed May 7, 2026, 10 p.m.
PD Predicate disambiguation batch_69fd0a3d68d4819094d92040f7c48d7c completed May 7, 2026, 9:55 p.m.
Created at: May 3, 2026, 4:16 p.m.