Triple
T9004014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foundation framework |
E215098
|
entity |
| Predicate | includes |
P1393
|
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 framework, includes, NSString]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NSString Context triple: [Foundation framework, includes, 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.
NSData
NSData is a fundamental Objective-C class in Apple’s Foundation framework that represents immutable raw binary data.
-
C.
STR
STR is the three-letter IATA airport code for Stuttgart Airport, the international airport serving Stuttgart, Germany.
-
D.
STR
STR is the common abbreviation for the Straubing Tigers, a professional ice hockey team based in Straubing, Germany.
-
E.
Core Text
Core Text is a macOS text layout and font-handling framework that provides low-level, high-performance text rendering and typographic capabilities for Cocoa 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6959497c8190a748c78504dd2eb6 |
completed | April 1, 2026, 12:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfd0e3f0c88190ae688632be25e5c9 |
completed | April 3, 2026, 2:38 p.m. |
Created at: March 30, 2026, 7:05 p.m.