Triple

T17702624
Position Surface form Disambiguated ID Type / Status
Subject Loch Neldricken E441345 entity
Predicate hasFolkloreAssociation P120146 FINISHED
Object local tales of hauntings 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: local tales of hauntings | Statement: [Loch Neldricken, hasFolkloreAssociation, local tales of hauntings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFolkloreAssociation
Context triple: [Loch Neldricken, hasFolkloreAssociation, local tales of hauntings]
  • A. includesFolklore chosen
    Indicates that one entity contains, incorporates, or features folklore as part of its content or composition.
  • B. folkloreFunction
    Indicates that something serves a role, purpose, or function within a body of folklore, such as myths, legends, or traditional narratives.
  • C. hasMythologicalBasis
    Indicates that something is founded on, derived from, or significantly influenced by a mythological story, figure, or tradition.
  • D. hasNameInReligionOrFolklore
    Indicates that an entity is known by a particular name specifically within a religious or folkloric tradition.
  • E. hasCulturalSignificanceFor
    Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
  • 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_69d8b9ea20b48190ace88bb46b01e6a9 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4715c3980819094b080a871df1100 completed April 19, 2026, 6:08 a.m.
PD Predicate disambiguation batch_69e3cde601d4819097903f471f1fe99a completed April 18, 2026, 6:31 p.m.
Created at: April 10, 2026, 10:05 a.m.