Triple

T18564549
Position Surface form Disambiguated ID Type / Status
Subject UTF-16 E453728 entity
Predicate moreSpaceEfficientThan P83524 FINISHED
Object UTF-32 for BMP-heavy text 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: UTF-32 for BMP-heavy text | Statement: [UTF-16, moreSpaceEfficientThan, UTF-32 for BMP-heavy text]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: moreSpaceEfficientThan
Context triple: [UTF-16, moreSpaceEfficientThan, UTF-32 for BMP-heavy text]
  • A. moreEfficientThan chosen
    Indicates that one entity performs a task or uses resources with greater efficiency than another entity.
  • B. isMoreEfficientThan
    Indicates that one entity performs a task or uses resources in a way that achieves the same or better outcome with less time, effort, or cost than another entity.
  • C. isLessEfficientThan
    Indicates that one entity performs a task or uses resources with lower efficiency compared to another entity.
  • D. offersMoreSpaceThan
    Indicates that one entity provides a greater amount of space or capacity than another entity.
  • E. lessOptimizedFor
    Indicates that one entity is designed, configured, or adapted to perform a task or function with lower efficiency or effectiveness compared to another entity.
  • 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_69d8d38974308190a9174430ef256b73 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53afd8114819093b57d86f8213311 completed April 19, 2026, 8:28 p.m.
PD Predicate disambiguation batch_69e478c16e0c8190b03966aa23c395a6 completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 11:42 a.m.