Triple

T27118889
Position Surface form Disambiguated ID Type / Status
Subject Biggleswade Common E686932 entity
Predicate isPublicAccessLand P36752 FINISHED
Object true 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: true | Statement: [Biggleswade Common, isPublicAccessLand, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isPublicAccessLand
Context triple: [Biggleswade Common, isPublicAccessLand, true]
  • A. isPublicLand chosen
    Indicates that a given area of land is owned or managed by a government or public authority and is accessible or designated for use by the general public.
  • B. hasNearbyPublicLand
    Indicates that one entity is located close to an area of public land, such as parks, reserves, or other publicly accessible open spaces.
  • C. isPublicInfrastructure
    Indicates that something is part of publicly accessible, collectively used facilities or systems typically provided or regulated by government for common use.
  • D. hasLandStatus
    Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
  • E. accessLandIncludes
    Indicates that one land access area or right encompasses or contains another within its scope.
  • 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_69ef148c2b588190afc15b529f7af845 completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69f6244119d0819081b22d365f9b907d completed May 2, 2026, 4:20 p.m.
PD Predicate disambiguation batch_69f61b40f02081909bd9c3ea73249163 completed May 2, 2026, 3:41 p.m.
Created at: April 27, 2026, 8:58 a.m.