Triple

T33041940
Position Surface form Disambiguated ID Type / Status
Subject Transport typeface E845489 entity
Predicate visualClassification P100400 FINISHED
Object humanist sans-serif 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: humanist sans-serif | Statement: [Transport typeface, visualClassification, humanist sans-serif]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: visualClassification
Context triple: [Transport typeface, visualClassification, humanist sans-serif]
  • A. aimOfClassification
    Indicates that one entity represents the purpose, goal, or intended outcome of a particular act or system of classification applied to another entity.
  • B. visualFeature
    Indicates a relationship where one entity possesses or exhibits a particular visual characteristic or attribute of another entity.
  • C. classificationConsensus
    Indicates that multiple agents or sources agree on the same classification or category assignment for a given entity or item.
  • D. classificationAccordingTo chosen
    Indicates that an entity is assigned a particular class, type, or category as defined or determined by a specified source, standard, or authority.
  • E. usedToClassify
    Indicates that one entity serves as a criterion or basis for categorizing or grouping 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_69f34951348c8190b56746b0a7018182 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d6a6b04c8190bee4cf9c00665ef7 completed May 3, 2026, 5:01 a.m.
PD Predicate disambiguation batch_69f6d27120988190aacec621cf2bf0e8 completed May 3, 2026, 4:43 a.m.
Created at: May 1, 2026, 1:24 a.m.