Triple
T9761908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSException |
E236689
|
entity |
| Predicate | conformsTo |
P3994
|
FINISHED |
| Object | NSCopying |
E820269
|
NE 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: NSCopying | Statement: [NSException, conformsTo, NSCopying]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NSCopying Context triple: [NSException, conformsTo, NSCopying]
-
A.
NSCopying
chosen
NSCopying is an Objective-C protocol that defines the interface for creating immutable copies of objects.
-
B.
NSMutableCopying
NSMutableCopying is an Objective-C protocol that allows objects to create mutable copies of themselves, typically used alongside the NSCopying protocol in Cocoa and Cocoa Touch frameworks.
-
C.
NSCoding
NSCoding is an Objective-C protocol in Apple’s frameworks that defines methods for encoding and decoding objects so they can be serialized and later reconstructed.
-
D.
NSSecureCoding
NSSecureCoding is an Apple protocol that extends NSCoding to require secure, type-checked archiving and unarchiving of objects to prevent object substitution attacks.
-
E.
NSCoder
NSCoder is an abstract class in Apple’s Foundation framework that provides an interface for encoding and decoding objects and values for archiving and serialization.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda04c70108190a8ed09eb6f2a124e |
completed | April 1, 2026, 10:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1d5a4a88c8190bac0a2bff02804dc |
completed | April 5, 2026, 3:23 a.m. |
Created at: March 30, 2026, 8:25 p.m.