Triple

T27293771
Position Surface form Disambiguated ID Type / Status
Subject Horsham E688700 entity
Predicate regionSpecialisation P21480 FINISHED
Object broadacre cropping 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: broadacre cropping | Statement: [Horsham, regionSpecialisation, broadacre cropping]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionSpecialisation
Context triple: [Horsham, regionSpecialisation, broadacre cropping]
  • A. regionSpecialization chosen
    Indicates that a region is designated or recognized as being particularly focused on, adapted to, or specialized in a specific function, activity, or domain.
  • B. specializationRegion
    Indicates that something is specialized, adapted, or specifically applicable to a particular geographic or spatial region.
  • C. rangeSpecialization
    Indicates that one entity is a more specific or constrained version of another entity within a defined range or scope.
  • D. regionException
    Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
  • E. regionSpecificContent
    Indicates that certain content is tailored, restricted, or applicable only to a particular geographic region or set of regions.
  • 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_69ef355a96308190a2bed991525fb278 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f7aa699d68819081ed363931894ab3 completed May 3, 2026, 8:04 p.m.
PD Predicate disambiguation batch_69f7a8cec6d48190bebfa884b2f938c0 completed May 3, 2026, 7:58 p.m.
Created at: April 27, 2026, 11:17 a.m.