Triple
T30315305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swift Playgrounds for iPad |
E771041
|
entity |
| Predicate | programmingLanguageTaught |
P176021
|
FINISHED |
| Object | Swift |
—
|
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: Swift | Statement: [Swift Playgrounds for iPad, programmingLanguageTaught, Swift]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmingLanguageTaught Context triple: [Swift Playgrounds for iPad, programmingLanguageTaught, Swift]
-
A.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
-
B.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
C.
hasLanguageOfProgramming
Indicates that an entity uses, is implemented in, or is otherwise associated with a particular programming language.
-
D.
languageOfPrimaryProgramming
Indicates the programming language that is primarily used to implement or develop a given entity.
-
E.
languageOfProgramming
Indicates that one entity is a programming language used to implement, develop, or script the other entity.
- F. None of above. chosen
Provenance (4 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 29, 2026, 7:51 p.m.