Triple
T27736627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.AssemblyVersionAttribute |
E697543
|
entity |
| Predicate | versionComponent |
P163537
|
FINISHED |
| Object | minor version |
—
|
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: minor version | Statement: [System.Reflection.AssemblyVersionAttribute, versionComponent, minor version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: versionComponent Context triple: [System.Reflection.AssemblyVersionAttribute, versionComponent, minor version]
-
A.
versionComponent
chosen
Indicates that one entity is a component or segment of another entity’s version identifier (e.g., major, minor, or patch number).
-
B.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
-
C.
versionFormat
Indicates the specific structural pattern or notation used to represent a version identifier.
-
D.
versionExample
Indicates that one entity serves as an example or illustrative instance of a particular version of another entity.
-
E.
versionField
Indicates that one entity serves as the version identifier or version-tracking field associated with another entity.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 3:13 p.m.