Triple

T27736625
Position Surface form Disambiguated ID Type / Status
Subject System.Reflection.AssemblyVersionAttribute E697543 entity
Predicate versionFormat P163168 FINISHED
Object major.minor.build.revision 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: major.minor.build.revision | Statement: [System.Reflection.AssemblyVersionAttribute, versionFormat, major.minor.build.revision]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: versionFormat
Context triple: [System.Reflection.AssemblyVersionAttribute, versionFormat, major.minor.build.revision]
  • A. versionOf
    Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
  • B. versionExample
    Indicates that one entity serves as an example or illustrative instance of a particular version of another entity.
  • C. exportVersion
    Indicates the specific release or revision identifier of an item as it is prepared for or used in export.
  • D. exportVersionOf
    Indicates that one entity is a version of another specifically created or designated for export (e.g., for external distribution or use).
  • E. versionField
    Indicates that one entity serves as the version identifier or version-tracking field associated with another entity.
  • 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_69ef590c3e288190ad54d2465af8ca4e completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f636a161608190b0cdf03863204034 completed May 2, 2026, 5:38 p.m.
PD Predicate disambiguation batch_69f63188e7408190af8ce8b93d128c63 completed May 2, 2026, 5:16 p.m.
PDg Predicate description generation batch_69f6352df6148190bc10772cd40bd7b3 completed May 2, 2026, 5:32 p.m.
Created at: April 27, 2026, 3:13 p.m.