Triple

T28310520
Position Surface form Disambiguated ID Type / Status
Subject SL9 E713979 entity
Predicate hasPerformanceProfile P181130 FINISHED
Object distinct performance profile compared to other G36 models 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: distinct performance profile compared to other G36 models | Statement: [SL9, hasPerformanceProfile, distinct performance profile compared to other G36 models]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPerformanceProfile
Context triple: [SL9, hasPerformanceProfile, distinct performance profile compared to other G36 models]
  • A. hasPerformanceElement
    Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
  • B. hasAbilityProfile
    Indicates that an entity is associated with a specific set or profile of abilities, skills, or capabilities.
  • C. hasPerformanceConvention
    Indicates that there is an agreed-upon set of rules, norms, or standards governing how a particular performance or activity should be carried out.
  • D. hasPerformanceLocation
    Indicates that an event, performance, or show takes place at a specified location or venue.
  • E. hasProfile
    Indicates that an entity is associated with or possesses a specific profile representation or account.
  • 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_69efb5256afc8190b9322d25c3ae6320 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f7626667f48190ad90867eb67ec582 completed May 3, 2026, 2:57 p.m.
PD Predicate disambiguation batch_69f76175d6608190b60b268e20f49ed9 completed May 3, 2026, 2:53 p.m.
PDg Predicate description generation batch_69f762651e088190baa21f25378a6065 completed May 3, 2026, 2:57 p.m.
Created at: April 27, 2026, 11:40 p.m.