Triple

T16395416
Position Surface form Disambiguated ID Type / Status
Subject Wentzville Assembly E398166 entity
Predicate hasLogisticsFacilities P78734 FINISHED
Object shipping and receiving docks 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: shipping and receiving docks | Statement: [Wentzville Assembly, hasLogisticsFacilities, shipping and receiving docks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLogisticsFacilities
Context triple: [Wentzville Assembly, hasLogisticsFacilities, shipping and receiving docks]
  • A. hasFreightFacility chosen
    Indicates that an entity is equipped with or connected to a facility used for handling, loading, unloading, or storing freight.
  • B. hasFacilities
    Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
  • C. hasFacilityLocation
    Indicates that an entity possesses or is associated with a facility situated at a specific location.
  • D. logisticsFeature
    Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
  • E. hasGoodsFacilities
    Indicates that a location or entity is equipped with facilities for handling, storing, or processing goods or cargo.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e326462298819087091dc935f0f916 completed April 18, 2026, 6:35 a.m.
PD Predicate disambiguation batch_69e226f94dd48190b7b8e0e983738a67 completed April 17, 2026, 12:26 p.m.
Created at: April 10, 2026, 5:08 a.m.