Triple

T6602660
Position Surface form Disambiguated ID Type / Status
Subject Leintwardine E149036 entity
Predicate hasLocalCharacter P71987 FINISHED
Object historic rural village 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: historic rural village | Statement: [Leintwardine, hasLocalCharacter, historic rural village]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocalCharacter
Context triple: [Leintwardine, hasLocalCharacter, historic rural village]
  • A. hasTextualCharacter
    Indicates that something possesses or exhibits the qualities of written or printed text, such as letters, symbols, or characters.
  • B. hasSpecialCharacter
    Indicates that a given entity (such as a string or identifier) contains at least one non-alphanumeric special character.
  • C. hasUnicode
    Indicates that an entity is associated with, represented by, or encoded using a specific Unicode character or sequence.
  • D. hasCanonicalCharacter
    Indicates that something is associated with or defined by its standard, officially recognized character representation.
  • E. hasUnicodeStatus
    Indicates that a given entity has a particular Unicode-related classification or status (such as assigned, reserved, deprecated, or noncharacter) within the Unicode standard.
  • 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_69c687eaa7508190bb58ce2aa02039b3 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6cc9c6cb0819084fec8e0beb430de completed March 27, 2026, 6:29 p.m.
PD Predicate disambiguation batch_69c6acfd17388190bd0bb8b2371e7df1 completed March 27, 2026, 4:14 p.m.
PDg Predicate description generation batch_69c6cc988c0081909d22b86ca299331c completed March 27, 2026, 6:29 p.m.
Created at: March 27, 2026, 1:56 p.m.