Triple

T5276575
Position Surface form Disambiguated ID Type / Status
Subject Cowfish Sushi Burger Bar E119384 entity
Predicate hasConceptElement P7161 FINISHED
Object sushi bar 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: sushi bar | Statement: [Cowfish Sushi Burger Bar, hasConceptElement, sushi bar]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasConceptElement
Context triple: [Cowfish Sushi Burger Bar, hasConceptElement, sushi bar]
  • A. hasConcept
    Indicates that an entity includes, embodies, or is associated with a particular concept.
  • B. hasSubConcept
    Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
  • C. hasCriticalConcept
    Indicates that one entity includes, depends on, or is defined by a key concept that is essential to understanding or functioning of another entity.
  • D. hasLinguisticElement chosen
    Indicates that one entity includes, is associated with, or is characterized by a particular linguistic component such as a word, phrase, symbol, or other language element.
  • E. hasSignatureConcept
    Indicates that something is associated with or characterized by a defining concept that uniquely represents its core meaning or identity.
  • 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_69bd446d05a8819092ad333a3f9c8d5c completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd8c9c72b08190947b6b955ac1bb5a completed March 20, 2026, 6:06 p.m.
PD Predicate disambiguation batch_69bd844a56b48190ad743c42246e02dd completed March 20, 2026, 5:30 p.m.
Created at: March 20, 2026, 1:51 p.m.