Triple

T6991553
Position Surface form Disambiguated ID Type / Status
Subject UTF-8 E162096 entity
Predicate ASCIICompatibility P66628 FINISHED
Object code points U+0000 to U+007F encoded as single bytes 0x00–0x7F 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: code points U+0000 to U+007F encoded as single bytes 0x00–0x7F | Statement: [UTF-8, ASCIICompatibility, code points U+0000 to U+007F encoded as single bytes 0x00–0x7F]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ASCIICompatibility
Context triple: [UTF-8, ASCIICompatibility, code points U+0000 to U+007F encoded as single bytes 0x00–0x7F]
  • A. ISOBasicLatinDerivative
    Indicates that one entity is a derivative or variant form of another entity within the ISO Basic Latin character set.
  • B. ISOBasicLatinOverlap chosen
    Indicates that two character sets or encodings share overlapping code points within the ISO Basic Latin (ASCII) range.
  • C. characterCoverage
    Indicates that one entity provides or includes sufficient representation or support for the characters (e.g., glyphs, symbols, or scripts) required or used by another entity.
  • D. asciType
    Indicates that one entity has a specific ASCII character type or classification in relation to another entity.
  • E. usesCharacterSet
    Indicates that one entity employs or relies on a specific character set defined by another entity for encoding or representing text.
  • 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_69c68856d7808190ab33ee914640281b completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dbc1f63c8190837cfd71cf5ed613 completed March 27, 2026, 7:34 p.m.
PD Predicate disambiguation batch_69c6d7c4a18881908d267137daed828b completed March 27, 2026, 7:17 p.m.
Created at: March 27, 2026, 2:32 p.m.