Triple

T33952565
Position Surface form Disambiguated ID Type / Status
Subject Brocklesby Park, Lincolnshire E870477 entity
Predicate hasArchitecturalContributionBy P42691 FINISHED
Object James Paine NE NERFINISHED

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: James Paine | Statement: [Brocklesby Park, Lincolnshire, hasArchitecturalContributionBy, James Paine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasArchitecturalContributionBy
Context triple: [Brocklesby Park, Lincolnshire, hasArchitecturalContributionBy, James Paine]
  • A. architecturalContribution
    Indicates a relationship where an entity contributes to the design, planning, or creation of an architectural work or feature.
  • B. architectIsNotableFor
    Indicates that an architect is recognized or distinguished for a particular work, contribution, or achievement.
  • C. hasLandmarkArchitect chosen
    Indicates that a landmark is associated with, or was designed by, a specific architect.
  • D. hasArchitecturalAward
    Indicates that an entity has received or been granted an architectural award.
  • E. architectNotedFor
    Indicates that an architect is recognized or distinguished for a particular work, style, contribution, or achievement.
  • 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_69f3499c2d7481909c953a5010227725 completed April 30, 2026, 12:22 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: May 1, 2026, 1:49 a.m.