Triple

T30578403
Position Surface form Disambiguated ID Type / Status
Subject Essex–Kent border area E778314 entity
Predicate containsIndustrialZone P146344 FINISHED
Object Tilbury industrial area 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: Tilbury industrial area | Statement: [Essex–Kent border area, containsIndustrialZone, Tilbury industrial area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containsIndustrialZone
Context triple: [Essex–Kent border area, containsIndustrialZone, Tilbury industrial area]
  • A. hasIndustrialZoneAlong
    Indicates that an industrial zone is located adjacent to or extending along the length of a specified linear feature (such as a road, river, or boundary).
  • B. hasIndustrialZoning
    Indicates that a given area or property is designated for industrial use under zoning regulations.
  • C. containsIndustrialAreas chosen
    Indicates that one entity includes or encompasses industrial areas within its boundaries or scope.
  • D. hasIndustrialAreaType
    Indicates that an entity’s industrial area is classified as a specific type or category of industrial zone.
  • E. isIndustrialAreaOf
    Indicates that a location functions primarily as an industrial zone or district associated with a specified area or jurisdiction.
  • 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_69f224a04b248190b0ca443ec86207b8 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69ff1d85441c8190931e758685a269f7 completed May 9, 2026, 11:41 a.m.
PD Predicate disambiguation batch_69ff1d186cc48190b315c61e23de6551 completed May 9, 2026, 11:40 a.m.
Created at: April 29, 2026, 8:23 p.m.