Triple
T32062593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Developer ecosystem |
E818781
|
entity |
| Predicate | legacyLanguage |
P28976
|
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: [Apple Developer ecosystem, legacyLanguage, Objective-C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legacyLanguage Context triple: [Apple Developer ecosystem, legacyLanguage, Objective-C]
-
A.
formerLanguage
chosen
Indicates that one entity was previously the language of another entity but is no longer in that role.
-
B.
heritageLanguage
Indicates that one entity is the ancestral or culturally inherited language associated with another entity.
-
C.
laterTraditionsLanguage
Indicates that later traditions or sources refer to or describe the subject using the specified language.
-
D.
traditionalLanguageName
Indicates the name traditionally used in a particular language to refer to the subject entity.
-
E.
hasLinguisticLegacy
Indicates that one entity has left a lasting influence or enduring impact on the language, linguistic practices, or linguistic development associated with another entity.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f757788190b3f55d91289b7fc1 |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:22 a.m.