Triple
T27736790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.AssemblyTrademarkAttribute |
E697547
|
entity |
| Predicate | metadataCategory |
P163534
|
FINISHED |
| Object | assembly identity and branding |
—
|
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 identity and branding | Statement: [System.Reflection.AssemblyTrademarkAttribute, metadataCategory, assembly identity and branding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metadataCategory Context triple: [System.Reflection.AssemblyTrademarkAttribute, metadataCategory, assembly identity and branding]
-
A.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
B.
metadataType
Indicates that one entity specifies the kind or category of metadata associated with another entity.
-
C.
textCategory
Indicates that a piece of text belongs to or is classified under a particular category or type.
-
D.
metadata
chosen
Indicates that one entity provides descriptive or contextual information about another entity, such as its properties, origin, or structure.
-
E.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
- 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.