Triple

T28584026
Position Surface form Disambiguated ID Type / Status
Subject Luna theme E723443 entity
Predicate usesDefaultFont P64886 FINISHED
Object Tahoma 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: Tahoma | Statement: [Luna theme, usesDefaultFont, Tahoma]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesDefaultFont
Context triple: [Luna theme, usesDefaultFont, Tahoma]
  • A. defaultFontOf
    Indicates that one entity is the standard or fallback font used for rendering text in another entity (such as a document, style, or interface element).
  • B. supportsParentFont
    Indicates that an entity provides or maintains compatibility with the font used by its parent entity.
  • C. typicalFontSupport
    Indicates that one entity (such as a system, application, or platform) normally includes or provides support for a particular font or set of fonts under standard conditions.
  • D. isDefaultFor chosen
    Indicates that something serves as the standard or fallback option that is automatically applied or selected for a given entity or context unless another choice is explicitly specified.
  • E. hasCalligraphy
    Indicates that an entity possesses or is associated with calligraphy, such as having calligraphic writing, decoration, or stylistic features.
  • 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_69f01d7f92e481909847f5f3f3174a89 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f67c9fe7b48190b79b4041357edb49 completed May 2, 2026, 10:37 p.m.
PD Predicate disambiguation batch_69f678cc272081909e5c70f1bc7407f0 completed May 2, 2026, 10:21 p.m.
Created at: April 28, 2026, 4:16 a.m.