Triple
T27731400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.AttributeUsageAttribute |
E697437
|
entity |
| Predicate | languageCSharpName |
P193930
|
FINISHED |
| Object | AttributeUsageAttribute |
—
|
NE NERFINISHED |
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: AttributeUsageAttribute | Statement: [System.AttributeUsageAttribute, languageCSharpName, AttributeUsageAttribute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageCSharpName Context triple: [System.AttributeUsageAttribute, languageCSharpName, AttributeUsageAttribute]
-
A.
languageName
Indicates the specific name assigned to a language in the relationship.
-
B.
componentNameLanguage
Indicates that a component’s name is expressed or recorded in a specific language.
-
C.
constantName
Indicates that an entity has a specific, fixed identifier or label used as a constant within a system or context.
-
D.
languageOfWorkOrName
Indicates the language in which a work is created or a name is expressed.
-
E.
codeNamespace
Indicates the namespace or modular grouping in which a piece of code or programming element is defined.
- F. None of above. chosen
Provenance (4 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_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 27, 2026, 3:11 p.m.