Triple

T3696975
Position Surface form Disambiguated ID Type / Status
Subject Guanggu E78481 entity
Predicate hasPolicySupport P49446 FINISHED
Object national high-tech zone policies 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: national high-tech zone policies | Statement: [Guanggu, hasPolicySupport, national high-tech zone policies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPolicySupport
Context triple: [Guanggu, hasPolicySupport, national high-tech zone policies]
  • A. supportsPolicy
    Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
  • B. hasReferencePolicy
    Indicates that an entity is governed by or associated with a specific reference policy that defines how it should be used, accessed, or managed.
  • C. hasPolicyOrientation
    Indicates that one entity (such as an organization, document, or actor) is characterized by or aligned with a particular policy stance, direction, or focus.
  • D. hasVisitorPolicy
    Indicates that an entity has an established policy governing the presence, behavior, or permissions of visitors.
  • E. hasKeyPolicy
    Indicates that an entity is associated with a specific key management or access control policy governing how its keys may be used or managed.
  • F. None of above. chosen

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_69ad85e3b1888190abc983e06968696d completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc5115ad8819085ffa938de3943f4 completed March 8, 2026, 6:50 p.m.
PD Predicate disambiguation batch_69adb84dc5808190850aa6975cb09e27 completed March 8, 2026, 5:56 p.m.
PDg Predicate description generation batch_69adb903be308190a8f1925f99e67c68 completed March 8, 2026, 5:59 p.m.
Created at: March 8, 2026, 3:26 p.m.