Triple
T30299950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSArray |
E770627
|
entity |
| Predicate | supportsKVC |
P207225
|
FINISHED |
| Object | YES |
—
|
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: YES | Statement: [NSArray, supportsKVC, YES]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsKVC Context triple: [NSArray, supportsKVC, YES]
-
A.
supportsKeyStorage
Indicates that an entity is capable of securely storing cryptographic keys or similar sensitive key material.
-
B.
keyValue
Indicates that one entity functions as a key that is associated with a corresponding value represented by the other entity.
-
C.
supportsValue
Indicates that one entity provides justification, evidence, or backing for the truth, relevance, or appropriateness of a particular value associated with another entity.
-
D.
supportsKeyManagement
Indicates that one entity provides functionality or capability to handle, store, or control cryptographic keys for another entity or process.
-
E.
supportsSerialization
Indicates that an entity is capable of being converted to and from a serialized form for storage or transmission.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 7:48 p.m.