Triple
T4326220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sns |
E96639
|
entity |
| Predicate | typicalImportStatement |
P20017
|
FINISHED |
| Object | import seaborn as sns |
—
|
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 seaborn as sns | Statement: [sns, typicalImportStatement, import seaborn as sns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalImportStatement Context triple: [sns, typicalImportStatement, import seaborn as sns]
-
A.
typicalImportName
chosen
Indicates that one entity is the conventional or commonly used import name (alias) for another entity in code.
-
B.
typicalEntryFile
Indicates that a given file is the standard or primary entry point typically used to start or access something (such as a program, project, or package).
-
C.
primaryImports
Indicates that one entity is the main or predominant source from which another entity imports goods, services, or resources.
-
D.
typicalSetup
Indicates that an entity is arranged, configured, or organized in its standard or commonly used setup relative to another entity or context.
-
E.
typicalProgramElement
Indicates that one program element is a representative or characteristic example of another program element or category of elements.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3513020f481909ff2fec3934f3002 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.