Triple
T17568896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | URLSession |
E427884
|
entity |
| Predicate | createsWith |
P74463
|
FINISHED |
| Object | URLSessionConfiguration.default |
—
|
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: URLSessionConfiguration.default | Statement: [URLSession, createsWith, URLSessionConfiguration.default]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createsWith Context triple: [URLSession, createsWith, URLSessionConfiguration.default]
-
A.
createdWith
chosen
Indicates that something was produced, built, or brought into existence using a particular tool, method, material, or resource.
-
B.
crea
Indicates that one entity creates, produces, or brings into existence another entity.
-
C.
coCreatedWith
Indicates that an entity participated jointly with another entity in the creation or production of something.
-
D.
createsWithin
Indicates that one entity brings another entity into existence or produces it while operating inside the spatial, temporal, or contextual bounds of a specified containing entity.
-
E.
creationType
Indicates the manner or process by which something was brought into existence or produced.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592f29d08190bc3de905d35af849 |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.