Triple

T37365376
Position Surface form Disambiguated ID Type / Status
Subject Harmony (Hexie) series E927695 entity
Predicate stillInUseFor P15255 FINISHED
Object many high-speed services in China 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: many high-speed services in China | Statement: [Harmony (Hexie) series, stillInUseFor, many high-speed services in China]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: stillInUseFor
Context triple: [Harmony (Hexie) series, stillInUseFor, many high-speed services in China]
  • A. stillUsedBy
    Indicates that something continues to be used or relied upon by another entity at the present time.
  • B. isInUse chosen
    Indicates that an entity is currently being utilized or actively engaged in its intended function or operation.
  • C. continuouslyUsedAs
    Indicates that one entity is persistently and repeatedly employed or utilized as another entity or for a particular function over an extended, uninterrupted period.
  • D. isSometimesUsedFor
    Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
  • E. areUsedIn
    Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
  • 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_69f76eb701788190b40824bc4594d985 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb9e1845e881908d19158440cf3b87 completed May 6, 2026, 8:01 p.m.
PD Predicate disambiguation batch_69fb8d08d6988190a00794ac26078348 completed May 6, 2026, 6:48 p.m.
Created at: May 3, 2026, 4:16 p.m.