Triple
T27737475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.MethodImplAttributes |
E697563
|
entity |
| Predicate | hasAttributeCategory |
P15481
|
FINISHED |
| Object | code type |
—
|
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: code type | Statement: [System.Reflection.MethodImplAttributes, hasAttributeCategory, code type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttributeCategory Context triple: [System.Reflection.MethodImplAttributes, hasAttributeCategory, code type]
-
A.
hasCategoryOn
chosen
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
B.
hasRecordCategory
Indicates that something is associated with, or classified under, a particular record category.
-
C.
hasCategoryGroup
Indicates that something is associated with, or belongs to, a broader grouping of related categories.
-
D.
hasCategoryLevel
Indicates that something is associated with a specific hierarchical category or tier within a classification system.
-
E.
haveCategoryCode
Indicates that an entity is associated with a specific classification or category identified by a code.
- 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_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 3:13 p.m.