Triple
T32123006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSFileHandle |
E820429
|
entity |
| Predicate | introducedForLanguage |
P35092
|
FINISHED |
| Object | Objective-C |
—
|
NE NERFINISHED |
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: Objective-C | Statement: [NSFileHandle, introducedForLanguage, Objective-C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedForLanguage Context triple: [NSFileHandle, introducedForLanguage, Objective-C]
-
A.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
B.
languageIntroduced
chosen
Indicates that a particular language was brought into use or made known within a certain context, time, or place.
-
C.
introducedLanguageElements
Indicates that an entity (such as a person, organization, or document) brought certain language elements (e.g., words, constructs, or features) into use or made them known for the first time.
-
D.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
E.
introducedSupportFor
Indicates that one entity initiated or implemented backing, assistance, or endorsement for another entity or concept.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 12:29 a.m.