Triple
T11957956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foundation |
E284599
|
entity |
| Predicate | includesType |
P121
|
FINISHED |
| Object | NSString |
E236682
|
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: NSString | Statement: [Foundation, includesType, NSString]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NSString Context triple: [Foundation, includesType, NSString]
-
A.
NSString
chosen
NSString is an Objective-C class representing immutable Unicode strings, widely used as the primary string type in Apple’s Cocoa and Cocoa Touch frameworks.
-
B.
CString
CString is a widely used MFC C++ class that provides convenient, high-level manipulation and management of character strings in Windows applications.
-
C.
NSArray
NSArray is an Objective-C class in Apple’s Foundation framework that represents an ordered, immutable collection of objects.
-
D.
NSData
NSData is a fundamental Objective-C class in Apple’s Foundation framework that represents immutable raw binary data.
-
E.
NSText
NSText is a fundamental Cocoa text-handling class in macOS development that provides the basic infrastructure for displaying, editing, and managing text in Application Kit–based applications.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903681a00819098c2b5260e2ef834 |
completed | April 10, 2026, 2:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f459210d1c8190953cd01da3d2ad04 |
completed | May 1, 2026, 7:41 a.m. |
Created at: April 8, 2026, 9:45 p.m.