Triple
T27737320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.PropertyAttributes |
E697559
|
entity |
| Predicate | valueOf_SpecialName |
P165718
|
FINISHED |
| Object | 512 |
—
|
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: 512 | Statement: [System.Reflection.PropertyAttributes, valueOf_SpecialName, 512]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueOf_SpecialName Context triple: [System.Reflection.PropertyAttributes, valueOf_SpecialName, 512]
-
A.
specialValue
Indicates that an entity possesses a distinguished or exceptional value compared to typical or default values in the given context.
-
B.
valueOfI
Indicates that one entity represents or corresponds to the specific value assigned to the variable or quantity denoted by "I".
-
C.
valueOfL
Indicates that one entity represents the numerical or quantitative value associated with another entity, typically in a specific context or measurement.
-
D.
hasNumberOfSpecials
Indicates that an entity is associated with a specific count of special items, features, or occurrences.
-
E.
symbolNumber
Indicates a relationship where a specific numerical identifier is assigned to or associated with a particular symbol.
- 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_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 27, 2026, 3:13 p.m.