Triple

T34793776
Position Surface form Disambiguated ID Type / Status
Subject OSGB36 E1003013 entity
Predicate localFit P181478 FINISHED
Object optimized for Great Britain landmass 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: optimized for Great Britain landmass | Statement: [OSGB36, localFit, optimized for Great Britain landmass]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: localFit
Context triple: [OSGB36, localFit, optimized for Great Britain landmass]
  • A. localFactorAt
    Indicates a relationship where a specific factor or influence is associated with, or applies at, a particular local point, position, or context.
  • B. localModelFor chosen
    Indicates that one entity serves as a localized or context-specific version or instance of another, more general model.
  • C. localityCondition
    Indicates a spatial or contextual constraint specifying where or under what local conditions a relationship, event, or property holds.
  • D. localSymmetry
    Indicates that an entity exhibits symmetry within a localized region or subset of its structure, rather than across its entire extent.
  • E. localBehavior
    Indicates that a behavior or effect is determined primarily by nearby or immediate context rather than by distant or global factors.
  • 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_69f76db543808190b188c6c86a91491b completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f78c61ed4c8190ad84c918fa9af55a completed May 3, 2026, 5:56 p.m.
PD Predicate disambiguation batch_69f78b8cb3a881909ebaac1b503988c2 completed May 3, 2026, 5:53 p.m.
Created at: May 3, 2026, 3:59 p.m.