Triple

T27736638
Position Surface form Disambiguated ID Type / Status
Subject System.Reflection.AssemblyVersionAttribute E697543 entity
Predicate appliedVia P80622 FINISHED
Object assembly-level attribute 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: assembly-level attribute | Statement: [System.Reflection.AssemblyVersionAttribute, appliedVia, assembly-level attribute]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliedVia
Context triple: [System.Reflection.AssemblyVersionAttribute, appliedVia, assembly-level attribute]
  • A. appliesVia chosen
    Indicates that an action, rule, or effect is carried out, implemented, or achieved through a specified method, medium, or mechanism.
  • B. appliedAs
    Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
  • C. appliedBy
    Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
  • D. appliedFrom
    Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
  • E. isAppliedBeyond
    Indicates that something (such as a rule, method, or effect) is used or has influence outside its original or primary scope, context, or boundary.
  • 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_69ef590c3e288190ad54d2465af8ca4e completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f7c29e1b848190b945c6c6120a5330 completed May 3, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69f7c1b6e7a881908deb96bedb2713f4 completed May 3, 2026, 9:44 p.m.
Created at: April 27, 2026, 3:13 p.m.