Triple
T29911535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLGeocoder |
E759684
|
entity |
| Predicate | swiftImport |
P128018
|
FINISHED |
| Object | import CoreLocation |
—
|
LITERAL 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: import CoreLocation | Statement: [CLGeocoder, swiftImport, import CoreLocation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: swiftImport Context triple: [CLGeocoder, swiftImport, import CoreLocation]
-
A.
frameworkImport
Indicates that one framework brings in and makes use of another framework as a dependency or component.
-
B.
moduleImport
chosen
Indicates that one module brings another module into its scope to use its definitions or functionality.
-
C.
importedWith
Indicates that one entity was brought into a system, context, or location together with or as part of another entity during an import process.
-
D.
primaryImports
Indicates that one entity is the main or predominant source from which another entity imports goods, services, or resources.
-
E.
allowsImports
Indicates that one entity permits another entity to bring in or receive items, data, or resources from an external source.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6775ac1ac8190a8efe5439cc1e52d |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:10 p.m.