Triple

T19046820
Position Surface form Disambiguated ID Type / Status
Subject Wall Drawing #1 E466156 entity
Predicate siteSpecificity P30375 FINISHED
Object designed for a particular wall 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: designed for a particular wall | Statement: [Wall Drawing #1, siteSpecificity, designed for a particular wall]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: siteSpecificity
Context triple: [Wall Drawing #1, siteSpecificity, designed for a particular wall]
  • A. isSiteSpecific chosen
    Indicates that something is designed, intended, or valid only for a particular location, context, or site and does not generally apply elsewhere.
  • B. specialistSiteOf
    Indicates that one entity is a specialized facility, location, or site dedicated to serving, supporting, or focusing on the other entity.
  • C. isSiteOf
    Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
  • D. siteTypeServed
    Indicates the type of site or location that is served, supported, or handled by a given entity or resource.
  • E. regionSpecialization
    Indicates that a region is designated or recognized as being particularly focused on, adapted to, or specialized in a specific function, activity, or domain.
  • 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_69d8dd040fb881909af2a964f65ad208 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d80466f88190988171920f2be7dc completed April 20, 2026, 7:38 a.m.
PD Predicate disambiguation batch_69e4b99633c8819097988608c278ecf8 completed April 19, 2026, 11:16 a.m.
Created at: April 10, 2026, 12:03 p.m.