Triple

T32387254
Position Surface form Disambiguated ID Type / Status
Subject COSCO-HIT Terminals E827574 entity
Predicate locatedAtTerminal P85899 FINISHED
Object Kwai Tsing Container Terminals E827571 NE 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: Kwai Tsing Container Terminals | Statement: [COSCO-HIT Terminals, locatedAtTerminal, Kwai Tsing Container Terminals]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedAtTerminal
Context triple: [COSCO-HIT Terminals, locatedAtTerminal, Kwai Tsing Container Terminals]
  • A. locatedAtTerminusOf
    Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
  • B. terminusLocatedOn
    Indicates that the endpoint or final stop of one entity (such as a route or line) is situated on or at another entity (such as a street, line, or location).
  • C. terminalLocation chosen
    Indicates the specific terminal or endpoint location associated with an entity or process.
  • D. locatedAtOutletOf
    Indicates that one entity is positioned at or directly adjacent to the outlet or discharge point of another entity (such as a flow, channel, or system).
  • E. terminusBLocation
    Indicates the location at which the B end or second endpoint of something (such as a route, connection, or segment) is situated.
  • F. None of above.

Provenance (4 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_69f349184e7481909c6c54428cb9cf12 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_6a02fcbe03d0819082d3dd715ed41623 completed May 12, 2026, 10:11 a.m.
NED1 Entity disambiguation (via context triple) batch_6a347b6d21a88190937022a2039f8852 completed June 18, 2026, 11:12 p.m.
PD Predicate disambiguation batch_6a02fc62138081908d2dbc5db7541d13 completed May 12, 2026, 10:09 a.m.
Created at: May 1, 2026, 12:51 a.m.