Triple
T18050840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | functools |
E431921
|
entity |
| Predicate | typicalImport |
P56540
|
FINISHED |
| Object | from functools import partial |
—
|
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: from functools import partial | Statement: [functools, typicalImport, from functools import partial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalImport Context triple: [functools, typicalImport, from functools import partial]
-
A.
typicalImportName
Indicates that one entity is the conventional or commonly used import name (alias) for another entity in code.
-
B.
moduleImport
Indicates that one module brings another module into its scope to use its definitions or functionality.
-
C.
importedWith
chosen
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.
typicalPackage
Indicates that something is the standard or commonly used package associated with a given entity or context.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff57ea08190a30a87993f7d3299 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.