Triple
T27867047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.AssemblyFileVersionAttribute |
E704382
|
entity |
| Predicate | metadataKind |
P44503
|
FINISHED |
| Object | assembly-level metadata |
—
|
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 metadata | Statement: [System.Reflection.AssemblyFileVersionAttribute, metadataKind, assembly-level metadata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metadataKind Context triple: [System.Reflection.AssemblyFileVersionAttribute, metadataKind, assembly-level metadata]
-
A.
metadataType
chosen
Indicates that one entity specifies the kind or category of metadata associated with another entity.
-
B.
metadata
Indicates that one entity provides descriptive or contextual information about another entity, such as its properties, origin, or structure.
-
C.
dataTypeContributed
Indicates that an entity has provided or supplied a particular type or category of data.
-
D.
metaProperty
Indicates that one property functions as a higher-level descriptor or attribute about another property, rather than about an entity directly.
-
E.
descriptorType
Indicates that one entity serves as a descriptive attribute or classification of 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 6:21 p.m.