Triple
T27736699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.AssemblyDescriptionAttribute |
E697545
|
entity |
| Predicate | attributeUsageTarget |
P164339
|
FINISHED |
| Object | Assembly |
—
|
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 | Statement: [System.Reflection.AssemblyDescriptionAttribute, attributeUsageTarget, Assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attributeUsageTarget Context triple: [System.Reflection.AssemblyDescriptionAttribute, attributeUsageTarget, Assembly]
-
A.
attributeUsageTargets
chosen
Indicates that a particular attribute is intended to be applied to, or is valid for use with, specific kinds of targets or elements.
-
B.
hasAttributeUsage
Indicates that an entity uses or applies a particular attribute in some context or manner.
-
C.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
D.
bindingTarget
Indicates that one entity serves as the specific object, site, or counterpart to which another entity binds or is bound.
-
E.
attributeType
Indicates that one entity specifies the kind or category of attribute that characterizes 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_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 3:13 p.m.