Triple
T27737321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.PropertyAttributes |
E697559
|
entity |
| Predicate | valueOf_RTSpecialName |
P165718
|
FINISHED |
| Object | 1024 |
—
|
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: 1024 | Statement: [System.Reflection.PropertyAttributes, valueOf_RTSpecialName, 1024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueOf_RTSpecialName Context triple: [System.Reflection.PropertyAttributes, valueOf_RTSpecialName, 1024]
-
A.
valueOf_SpecialName
chosen
Indicates that one entity represents the specific or special name value assigned to another entity.
-
B.
Unmanaged32Bit_value
Indicates that the value is stored or handled as an unmanaged 32-bit quantity, without automatic memory or resource management.
-
C.
codeUnitType
Indicates the specific kind or category of a code unit (such as a file, class, method, or module) that a given element belongs to.
-
D.
specialValue
Indicates that an entity possesses a distinguished or exceptional value compared to typical or default values in the given context.
-
E.
valueOfI
Indicates that one entity represents or corresponds to the specific value assigned to the variable or quantity denoted by "I".
- 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_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 3:13 p.m.