Triple

T5882297
Position Surface form Disambiguated ID Type / Status
Subject Unicode 5.1 E130775 entity
Predicate refinesSupportFor P67237 FINISHED
Object existing scripts 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: existing scripts | Statement: [Unicode 5.1, refinesSupportFor, existing scripts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: refinesSupportFor
Context triple: [Unicode 5.1, refinesSupportFor, existing scripts]
  • A. providesSupportTo
    Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
  • B. supportedIn
    Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
  • C. isSupportedBy
    Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
  • D. supportsImplementationOf
    Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
  • E. supportedAs
    Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
  • 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_69c0085523688190bfd487479ce819e6 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03fe07b7081909f8577ec3a9a1a8d completed March 22, 2026, 7:15 p.m.
PD Predicate disambiguation batch_69c0334bdc308190ad0d7199ab975588 completed March 22, 2026, 6:22 p.m.
PDg Predicate description generation batch_69c03fdf954c8190ae97a5c9ce40bdfa completed March 22, 2026, 7:15 p.m.
Created at: March 22, 2026, 3:57 p.m.