Triple

T38160413
Position Surface form Disambiguated ID Type / Status
Subject Zapfino Arabic E953000 entity
Predicate designedAsCompanionFor P200466 FINISHED
Object Zapfino Latin script NE NERFINISHED

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: Zapfino Latin script | Statement: [Zapfino Arabic, designedAsCompanionFor, Zapfino Latin script]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedAsCompanionFor
Context triple: [Zapfino Arabic, designedAsCompanionFor, Zapfino Latin script]
  • A. designedToAccompany chosen
    Indicates that one entity is created or intended specifically to be used, experienced, or present together with another entity.
  • B. companionOf
    Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
  • C. hasCompanionPiece
    Indicates that one item is conceptually or functionally paired with another item as its companion piece.
  • D. hasCompanionBook
    Indicates that one entity (typically a primary work) is associated with another entity that serves as its companion book, providing supplementary or related content.
  • E. includesCompanion
    Indicates that one entity involves, contains, or is accompanied by another entity acting as a companion.
  • 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_69f76f0b93c48190a117319ab3a9f282 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69ff956dc6548190979171d4b4068d47 completed May 9, 2026, 8:13 p.m.
PD Predicate disambiguation batch_69ff93dc39c481908a97a12c3ef7dfe7 completed May 9, 2026, 8:06 p.m.
Created at: May 3, 2026, 4:21 p.m.