Triple

T35047804
Position Surface form Disambiguated ID Type / Status
Subject Rambler Channel E1011247 entity
Predicate navigationRules P40609 FINISHED
Object Hong Kong local shipping regulations 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: Hong Kong local shipping regulations | Statement: [Rambler Channel, navigationRules, Hong Kong local shipping regulations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: navigationRules
Context triple: [Rambler Channel, navigationRules, Hong Kong local shipping regulations]
  • A. navigationType
    Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
  • B. navigationRegulation chosen
    Indicates rules or constraints that govern how navigation or movement is allowed, restricted, or managed within a particular space or system.
  • C. navigationSupport
    Indicates that one entity provides assistance, guidance, or tools to help another entity navigate or find its way.
  • D. navigationControlBy
    Indicates that one entity directs, manages, or influences the navigation or movement of another entity.
  • E. navigationFrom
    Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
  • 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_69f76dcfdda48190b1ebae5da8b54f12 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f785c8cdcc819081479fad0a3a23a0 completed May 3, 2026, 5:28 p.m.
PD Predicate disambiguation batch_69f7841812f081909d878955d114088e completed May 3, 2026, 5:21 p.m.
Created at: May 3, 2026, 4:01 p.m.