Triple

T29480241
Position Surface form Disambiguated ID Type / Status
Subject Ghastly Good Taste E747760 entity
Predicate positionOnVictorianArchitecture P194939 FINISHED
Object defensive 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: defensive | Statement: [Ghastly Good Taste, positionOnVictorianArchitecture, defensive]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: positionOnVictorianArchitecture
Context triple: [Ghastly Good Taste, positionOnVictorianArchitecture, defensive]
  • A. locationInArchitecture
    Indicates the spatial position or placement of one architectural element or feature within or relative to another architectural structure or context.
  • B. positionOnModernArchitecture chosen
    Indicates a stance, opinion, or evaluative view that an entity holds regarding modern architecture.
  • C. builtHeritage
    Indicates a relationship where a structure or site is recognized as part of the historically or culturally significant built environment.
  • D. Porteous BuildingLocation
    Indicates that a Porteous building is located at or associated with a specific geographic place or address.
  • E. architecturalLegacyIn
    Indicates that an entity has left a lasting architectural influence, style, or heritage within a specified place or region.
  • 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_69f0bd43ba30819095eb1cfc3adf525c completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69fd974d75e08190af46b1d608769f3b completed May 8, 2026, 7:57 a.m.
PD Predicate disambiguation batch_69fd94ff792c8190bedf4a639d3da809 completed May 8, 2026, 7:47 a.m.
Created at: April 28, 2026, 4:03 p.m.