Triple
T37657397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .NET X509Store class |
E937635
|
entity |
| Predicate | supportsStoreName |
P96685
|
FINISHED |
| Object | My |
—
|
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: My | Statement: [.NET X509Store class, supportsStoreName, My]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStoreName Context triple: [.NET X509Store class, supportsStoreName, My]
-
A.
supportsNameType
chosen
Indicates that one entity is capable of handling, recognizing, or being associated with a particular type or category of name.
-
B.
supportsKeyStorage
Indicates that an entity is capable of securely storing cryptographic keys or similar sensitive key material.
-
C.
supportsStoredValue
Indicates that an entity is capable of holding, managing, or processing stored monetary or credit value for later use.
-
D.
storeType
Indicates the category or kind of store associated with an entity, such as its retail or service type.
-
E.
supportsDatastoreType
Indicates that one entity is capable of working with, handling, or being compatible with a specified type of datastore.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.