Triple

T7873648
Position Surface form Disambiguated ID Type / Status
Subject Davo E182797 entity
Predicate orthographicPattern P79494 FINISHED
Object baseNamePlus-oSuffix 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: baseNamePlus-oSuffix | Statement: [Davo, orthographicPattern, baseNamePlus-oSuffix]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: orthographicPattern
Context triple: [Davo, orthographicPattern, baseNamePlus-oSuffix]
  • A. orthographicProperty
    Indicates a relationship where a specific written or spelling-related characteristic is attributed to or associated with an entity.
  • B. orthographicVariant
    Indicates that two written forms are different spellings or orthographic representations of the same linguistic item.
  • C. hasOrthographicConvention
    Indicates that there is a specific writing or spelling convention that governs how something is represented in written form.
  • D. orthographicRole
    Indicates the functional role that a written form or spelling plays within an orthographic system (e.g., as a letter, diacritic, punctuation mark, or other script element).
  • E. hasOrthographicReform
    Indicates that an entity has undergone or is associated with a change or standardization in its writing system or spelling conventions.
  • F. None of above. chosen

Provenance (4 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_69ca828a17248190b46defe758bc5ad3 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb39a7f1648190980db4db1a800189 completed March 31, 2026, 3:04 a.m.
PD Predicate disambiguation batch_69cae928e1b88190b0620f4c4f03bc7d completed March 30, 2026, 9:20 p.m.
PDg Predicate description generation batch_69caf786ec748190b6347b0c94335550 completed March 30, 2026, 10:21 p.m.
Created at: March 30, 2026, 4:56 p.m.