Triple

T49191
Position Surface form Disambiguated ID Type / Status
Subject Salem Village E966 entity
Predicate presentIn P795 FINISHED
Object Danvers, Massachusetts historic districts 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: Danvers, Massachusetts historic districts | Statement: [Salem Village, presentIn, Danvers, Massachusetts historic districts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: presentIn
Context triple: [Salem Village, presentIn, Danvers, Massachusetts historic districts]
  • A. presentedBy
    Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
  • B. appearsIn chosen
    Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
  • C. featuredIn
    Indicates that one entity appears or is prominently included within another entity, such as a person, work, or item being showcased in a larger work, event, or context.
  • D. fieldPresenceIn
    Indicates that something exists or is located within a particular field, area, or domain.
  • E. providedFor
    Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
  • 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_69a2480baefc81909951b14058479aa2 completed Feb. 28, 2026, 1:42 a.m.
NER Named-entity recognition batch_69a24c1a5c14819088748317a3f262c8 completed Feb. 28, 2026, 1:59 a.m.
PD Predicate disambiguation batch_69a24abfa7bc8190932c137a823efcb6 completed Feb. 28, 2026, 1:54 a.m.
Created at: Feb. 28, 2026, 1:47 a.m.