Triple

T7799790
Position Surface form Disambiguated ID Type / Status
Subject Sabine River E180397 entity
Predicate hasIndustrialCorridor P31150 FINISHED
Object lower Sabine River area 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: lower Sabine River area | Statement: [Sabine River, hasIndustrialCorridor, lower Sabine River area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasIndustrialCorridor
Context triple: [Sabine River, hasIndustrialCorridor, lower Sabine River area]
  • A. isIndustrialCorridor chosen
    Indicates that an area or route is designated and used primarily for industrial activities, facilities, or transportation.
  • B. hasIndustrialPark
    Indicates that a location or entity possesses or contains an industrial park within its area or jurisdiction.
  • C. isIndustrialRegion
    Indicates that a given area functions primarily as a center of industrial activity, characterized by significant manufacturing, production, or related industrial operations.
  • D. hasIndustrialAreaType
    Indicates that an entity’s industrial area is classified as a specific type or category of industrial zone.
  • E. hasIndustrialSector
    Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
  • 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_69ca827e50cc8190a92a733577184938 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69caf78a6d88819093f83528fe88b182 completed March 30, 2026, 10:22 p.m.
PD Predicate disambiguation batch_69cae9111b2481909684a2d4aa4831c2 completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 4:33 p.m.